Nested API Button open form to add input, check box and redirect back to original form
I have another API Button question...similar to my last question. Using the same table set up (below), but this time the button would be selected if it's for a license that would not be applicable and input from the User would be required. I created a simple table that would pop up when the button was pushed asking the User to add information into the field. It would also check the [Not Applicable] button, then refresh back to the original page. However, I get the attached error page. Any thoughts? License Master(parent table) Pending Locations(parent table Suggested Licenses(a child (many to many table) to both above) Licenses (child (many to many table) to both License Master and Pending Locations / unrelated to Suggested Licenses) var text UpdateSuggestedLicense=URLRoot() & "db/" & [_DBID_SUGGESTED_LICENSES] & "?act=API_EditRecord" & "&rid=" & URLEncode([Record ID#]) & "&_fid_18=true" //Check Not Applicable to this Location & "&apptoken=MY TOKEN" & "&rdr=" & URLEncode(URLRoot() & "db/" & Dbid() & "?a=dr&rid=" & [Record ID#]); var text OPEN="<a class=\"OpenAsPopup\" data-height=900 data-width=900 href='" & Dbid() & "?a=API_EditRecord&rid=" & [Record ID#] // Suggested License ID & "&dfid=11" // Not Applicable form ID & "&apptoken=MY TOKEN"; var text RefreshPage = URLRoot() & "db/" & Dbid() & "?a=doredirect&z=" & Rurl();//refresh and redirect back to License page $OPEN &"&rdr=" & URLEncode($UpdateSuggestedLicense) & URLEncode("&rdr=" & URLEncode($RefreshPage))
Quickbooks Online Authorization: Auth2.0 Tokens expiring after 24hrs
Getting an "invalid_grant" error after 24hrs. For the life of me I cannot figure out how to keep the tokens working past 24hrs. This pipeline runs every hour and returns updated refresh and access tokens. Everything works fine for 24hrs. This is from Inutuit Dev: "Tip: We update the value of the refresh_token value every 24 hours hours, or the next time you refresh the access tokens after 24 hours. This is an additional security measure by Intuit to reduce risk of compromise." Somehow refreshing both every hour is not meeting this requirement? We had a pipeline running every 12hrs also to get a refresh token separately but the results were the same. I feel like we are close, but just missing the timing of the pipelines or something else simple. PLEASE HELP!! I can provide more information beyond the two attachments as needed.Pass international phone format while updating phone number with Quickbase Restful API
I need to pass phone numbers from a 3rd party app to Quickbase via the Restful API. We receive phone numbers from outside the United States, so I need to pass in the country format as well as the phone number. After all my research, it seems like you can only change the country format through the Quickbase user interface. However, if there is a way to not have users do double the work, that would be ideal.UPSERT Order processing preferences
When a Quickbase server gets a large UPSERT via API, how does the server perform the process/calculation to locate the correct Record ID# and determine whether to update/add the record in the table? Does the Quickbase system have a preference for the order of records? I'm thinking about what uses more processing in terms of an UPSERT. When I API a bulk UPSERT to a QB table leveraging a UNIQUE field (not the Record ID#) what is the preferred sort order of the records UPSERTED? I can sort using the UNIQUE field. I can sort using Record ID#. I can not sort. Wonder if anyone at Quickbase has performed this type of test and measured the performance?
Using Webhooks
Hello, This is a very general question, but I would like to integrate QuickBase with our maintenance program Upkeep. Specifically, I would like to create work order requests in QuickBase that can automatically create one in Upkeep. Is this possible? I do not have much experience with webhooks but would love to learn if this is even possible before I go down that path. Thank you, and any help would be greatly appreciated.Document creation - Save PDF to field in record
Loving the new Document creation feature, but now I want to expand upon it and save the generated PDF to a file attachment field on the form. The feature just makes an API call and the PDF is returned in the response, so we should be able to build a Pipeline to iterate through the JSON response and save the PDF. I've been trying to set this up for a few days, but to no avail. Has anyone done this yet?
API_AddRecord Then Redirec To Dashboard
Greetings, I have been searching and experimenting for some time now. I have given up and decided to try posting, as everything I have found is not working so far. I have a dashboard that I would like to add a button to. The button is intended to make an API_AddRecord call and then return to the dashboard. I can get the API_AddRecord URL together and it works as intended. The desired record will be added successfully. I have the URL to bring up the dashboard as well. What I can't get to work putting them both in a formula URL that will return the page to the dashboard after the call is made. Can someone give me the structure for how this is to work? Thank you in advance for any input / direction you can provide. James
