Forum Discussion

RyanFarrington's avatar
RyanFarrington
Qrew Member
4 years ago

Is there a limit to number of fields you can specify in a GET-method API_AddRecord?

I'm making a button that creates a new record using the GET method. I'm using API_AddRecord. I want to specify the values for 13 fields, but it seems the operation stops after 7 fields. It creates the record, but without the 6 remaining fields filled out, and it doesn't go on to the proper redirect I specify.

This makes me suspect there is a limit to the number of fields you can specify in in a GET API_AddRecord operation.

Questions:
1) is this true--on purpose?
2) is this true--as a bug?
3) can I use a different method to specify more fields and give me the redirect I want?

------------------------------
Ryan Farrington
Graphic designer, project manager, copywriter, engraver, internal Quick Base developer
rfarrington@experiencepinpoint.com
------------------------------
APIs and custom code

9 Replies

Sort By
  • MarkShnier__You's avatar
    MarkShnier__You
    Icon for Qrew Legend rankQrew Legend
    4 years ago
    Can we see your current code / formula?

    ------------------------------
    Mark Shnier (YQC)
    Quick Base Solution Provider
    Your Quick Base Coach
    http://QuickBaseCoach.com
    mark.shnier@gmail.com
    ------------------------------
    • RyanFarrington's avatar
      RyanFarrington
      Qrew Member
      4 years ago
      Below is the code. I used to have field 89, a required field, in spot number 8, and no matter what I put in field 89 I got error 50, saying that required field 89 was blank. I moved it to the beginning of the list and now the record gets created. But the Billing Address doesn't get populated in the new client record. Quick Base also just returns me to the XML output page instead of redirecting.

      var text URLONE = // create the client
          URLRoot() & "db/" & [_DBID_CLIENTS] & "?a=API_AddRecord&apptoken=XXXXXXXXXXXXXXXXXXXXXXXXX"
          & "&_fid_89=" & [Related Payment Term]
          & "&_fid_99=" & [Tax Code]
          & "&_fid_6=" & [Company Name]
          & "&_fid_62=" & [Lead Source]
          & "&_fid_126=" & UserToEmail(User())
          & "&_fid_33=Prospect"
          & "&_fid_38=" & URLEncode([Industry])
          & "&_fid_37=" & [Website]
          & "&_fid_43=" & UserToEmail(User()) //Account Lead
          & "&_fid_83=" & UserToEmail(User()) //Project Manager
          & "&_fid_18=" & [Billing Address]
          & "&_fid_25=" & [Billing Address]
          & "&_fid_173=" & [Record ID#]
          ;
      var text URLTWO = ... 

      "<ahref='javascript:LinkAway(\""
          & $URLONE & "&rdr=" & URLEncode($URLTWO)
      & "\");'>Confirm info & add opportunity</a>"

      ------------------------------
      Ryan Farrington
      Graphic designer, project manager, copywriter, engraver, internal Quick Base developer
      rfarrington@experiencepinpoint.com
      ------------------------------
      • MarkShnier__You's avatar
        MarkShnier__You
        Icon for Qrew Legend rankQrew Legend
        4 years ago
        I suggest that you URLEncode and field which has the possibility to contain special characters or spaces.

        var text URLONE = // create the client
            URLRoot() & "db/" & [_DBID_CLIENTS] & "?a=API_AddRecord&apptoken=XXXXXXXXXXXXXXXXXXXXXXXXX"
            & "&_fid_89=" & [Related Payment Term]
            & "&_fid_99=" & [Tax Code]
            & "&_fid_6=" & urlencode([Company Name])
            & "&_fid_62=" & urlencode([Lead Source])
            & "&_fid_126=" & UserToEmail(User())
            & "&_fid_33=Prospect"
            & "&_fid_38=" & URLEncode([Industry])
            & "&_fid_37=" & urlencode([Website])
            & "&_fid_43=" & UserToEmail(User()) //Account Lead
            & "&_fid_83=" & UserToEmail(User()) //Project Manager
            & "&_fid_18=" & urlencode([Billing Address])
            & "&_fid_25=" & urlencode([Billing Address])
            & "&_fid_173=" & [Record ID#]
            ;


        var text URLTWO = ....;

        $URLONE
        & "&rdr=" & URLEncode($URLTWO)



        I don't use your syntax with the linkaway so i don't know if that will work or not.

        ------------------------------
        Mark Shnier (YQC)
        Quick Base Solution Provider
        Your Quick Base Coach
        http://QuickBaseCoach.com
        mark.shnier@gmail.com
        ------------------------------