Forum Discussion
MarkShnier__You
Qrew Legend
Exactly. I prfer to line them up vertically for readability
I have a 'Add Button' like this:
URLRoot() & "db/" & [_DBID_JOINS] & "?a=API_GenAddRecordForm"
& "&_fid_10=" & URLEncode ([Record ID#])
& "&_fid_11=1"
& "&_fid_12=" & URLEncode ([Customer Priority])
& "&_fid_99=false"
& "&dfid=11 &z=" & Rurl()
The & sign at the beginning of each line is concatenation to be able to continue the string on the next line.
The & inside the quote says to Quickbase "hey QB, here is a parameter comin' at you and its a Field ID# and its for field ID 99 and then here is the value to load into that field.
You are building a URL string that has to survive travelling through the whole Internet. So if any of the contents of the value of your stuffing into the field has illegal characters like even spaces or some of the characters on the top row of the keyboard then you need to URLEncode them. For example in all the online shopping you'll ever do you will never see a space in the URL when you're on Amazon. URLs don't have spaces and similarly, other characters are not legal either for URLs
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------
I have a 'Add Button' like this:
URLRoot() & "db/" & [_DBID_JOINS] & "?a=API_GenAddRecordForm"
& "&_fid_10=" & URLEncode ([Record ID#])
& "&_fid_11=1"
& "&_fid_12=" & URLEncode ([Customer Priority])
& "&_fid_99=false"
& "&dfid=11 &z=" & Rurl()
The & sign at the beginning of each line is concatenation to be able to continue the string on the next line.
The & inside the quote says to Quickbase "hey QB, here is a parameter comin' at you and its a Field ID# and its for field ID 99 and then here is the value to load into that field.
You are building a URL string that has to survive travelling through the whole Internet. So if any of the contents of the value of your stuffing into the field has illegal characters like even spaces or some of the characters on the top row of the keyboard then you need to URLEncode them. For example in all the online shopping you'll ever do you will never see a space in the URL when you're on Amazon. URLs don't have spaces and similarly, other characters are not legal either for URLs
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------
RyanLocke1
4 years agoQrew Cadet
Mark,
That worked like a charm! I had another question...in my join table I am trying to change the name so it doesn't say 'Add Join' and make it more pertinent to the form I'm using. I'm wanting it to say 'Add Contract' any thoughts?
------------------------------
Ryan Locke
------------------------------
That worked like a charm! I had another question...in my join table I am trying to change the name so it doesn't say 'Add Join' and make it more pertinent to the form I'm using. I'm wanting it to say 'Add Contract' any thoughts?
------------------------------
Ryan Locke
------------------------------
- LauraThacker4 years agoQrew CaptainRyan,
This setting is in your ADVANCED settings of your Table. You have a "Table name", a "Records in this table are called" and "A single record is called". You want to change the last one; which will change the way the record "Add a xxxx" displays without changing the table menu bar name. Put this in your URL at the end of your dbid: ?a=KeyProps to get to that screen.
------------------------------
Laura Thacker (IDS)
laura@intelligentdbs.com
(626) 771 0454
------------------------------- RyanLocke14 years agoQrew CadetHey Laura,
Thank you for the reply. What if this is acting as a join table for multiple tables and I have different forms for different types of records that will be added. I have one form that is 'Add Contract', another that will be 'Add Owner', and so forth.
Best,
Ryan
------------------------------
Ryan Locke
------------------------------- LauraThacker4 years agoQrew CaptainUnfortunately you cannot make it appear differently based on a Form, or a Role; it is a table-level setting.
However; if you make it even more "generic" such as "new record", "new entry" or "record"; you can always use a TEXT element on a form with customized color, font-weight, font-family and height, to let the user know that they are "ADD A CONTRACT" which only appears on that specific Form which is then attributed to the users who use that form. It's not ideal since it requires more customization and essentially presents the same information twice; but you might find that with a larger "notice" at the top of the form (in color) users will probably ignore the default-header option.
------------------------------
Laura Thacker (IDS)
laura@intelligentdbs.com
(626) 771 0454
------------------------------