Qrew LegendThere is nothing different about EOTI in terms of the syntax of the API.
Hi Mark.
Thanks.
Once a record has been added how can we display the record and associated form, the form it was created with, in edit and view modes?
Tim
------------------------------
Tim Egerton
------------------------------
Qrew LegendOK, now I understand the true nature of your problem. You have one table but you are trying to allow the users to interact on a trilingual basis.
This is actually a very interesting challenge. If you try to use the multiple form approach then there are only really two ways to control which form is used. One is my role but in your case these are EOTI users so they are all in the same role and one is by report. I can't really see how that second option is useful in your case.
I actually think the best solution in your case is to have formula fields to calculate floating labels for the input fields. So the very first field on the form would be a multiple-choice field for the language. So for example English French and Spanish might be the three choices. The Dashboard button to Add a record would contain syntax to populate those fields.
So or example if the language Field ID was #10, then
https://TARGET DOMAIN/db/bqwga5efh?a=API_GenAddRecordForm&_fid_10=Spanish
Then what you would do is arrange your fields probably vertically on the form so that the first column of fields would actually be formula fields that would calculate the label for the field and then the field right beside it would have its own native label suppressed (so no label showing) using the form properties.
Here is an example of he formula for he floating label. Quick Base is a bit unpredictable with accented characters, so in the end you may need to forgo the accents.
Case([Language],
"French", "Prénom",
"Spanish", "Primer Nombre",
"English", "First Name")
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
Hi Mark,
Thanks for the reply.
A bit more information might be helpful.
The app is for international travel into a country.
The form is in two parts (Tabs) (a) initial registration of interest to travel and (b) health declaration relating to COVID.
Part (a) can be done at anytime while part (b) must be done within 24 hours of actual travel.
We have copied the form and used Alt Text to display three languages, all record fields remain the same.
Part (a) involves initial record creation and displays the first Tab only.
We have three buttons on the EOTI home page each linked to the respective "language" form using APIGenAddRecordFrom.
For part (b) we are using a search widget with exact match on First Name, Last Name and Passport Number.
This returns the record for editing and displays both Tabs.
However it is not bring the form used to create the record i.e. if the Spanish form was used to create the record in edit it is displaying the English form.
We have tried adding a formula url field to each form as follows URLRoot()&"db/"&Dbid()&"?a=dr&rid="&ToText([Record ID#])&"&dfid=11" were dfid=11 is the French form. But no success.
Tim
------------------------------
Tim Egerton
------------------------------
Qrew LegendI will need to better understand your workflow. I think that we can get this to work if the buttons on the Dashboard return the user to the Dashboard after the save as opposed to displaying the saved record on the wrong form.
Is that your issue that when the record is initially saved, it displays on an incorrect form as opposed to landing the user on some kind of Thank You page?
