Forum Discussion

EOMDevelepors's avatar
EOMDevelepors
Qrew Captain
7 years ago

change the native add record button to go to a certain form instead of using the one this table is set to be used in view mode.

I want to change the native add record button to direct to a certain form. I know I can do tht by changing the entire report to use a certain form but I don't want to do that since I still want for vi...
Formulas and functions
TateForgey's avatar
TateForgey
Qrew Assistant Captain
5 years ago
Am I right that the "dfid" ability to specify a form is not available in the API_ GenAddRecordForm?  It doesn't look like it in the API documentation and I can't get it to work, but I was just hoping. 

I need to direct people in the same role to different forms and then redirect to different places after completing the form and I was hoping to specify that all in the button.  I'll try to use form rules based on lookup fields that may be different if I have to, but just making sure there wasn't an easier way.

------------------------------
Tate Forgey
------------------------------
MarkShnier__You's avatar
MarkShnier__You
Icon for Qrew Legend rankQrew Legend
5 years ago
To answer your first question you can certainly control the form in that API. 

API_ GenAddRecordForm&dfid=10  etc will work just fine.



------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
  • TateForgey's avatar
    TateForgey
    Qrew Assistant Captain
    5 years ago
    Okay - thanks.  I must have had some syntax wrong because it was just going to the main form.  Doing it with form rules worked out, but this is good to know.  There are instances where you don't want to treat everyone in the "Everyone on the Internet" role the same way.

    ------------------------------
    Tate Forgey
    ------------------------------
  • TateForgey's avatar
    TateForgey
    Qrew Assistant Captain
    2 years ago

    Confirming this was a syntax issue. 

    There is inconsistency in the way that the underscores are used in the field vs. the form identifier. Look out for the use of those underscores.