Save & Redirect in a Formula URL Using API_GenAddRecordForm
Hi. I have a need to "duplicate" the record and populate some fields on the new record (from the original record). It's not saving my current record before adding the new record, how do I get it to save first? I have the advanced setting turned on. This is my Formula URL Button: If( [Request] = "Include Existing Contractor + Add NEW FTE for Conversion", URLRoot() & "db/" & Dbid() & "?a=API_GenAddRecordForm" & "&_fid_53=" & URLEncode([Related Business case]) & "&_fid_129=60" & // Softcode the Months Needed to 60 FTE "&_fid_68=This Request is related to " & URLEncode([Request]) & "&_fid_123=14" & // Sets Request to "New FTE (Related Conversion)" "&_fid_127=FTE" & // New Employee Type "&_fid_43=" & URLEncode([Contractor PID - Dept]) & "&_fid_139=" & URLEncode([Related Level]) & "&_fid_138=" & URLEncode([Related Role]) & "&_fid_140=" & URLEncode([Related Hiring Manager]) & "&_fid_171=1" & // Start Date Override Checkbox to Yes "&_fid_259=" & URLEncode([Record ID#]), If( [Request] = "Add New Contractor + Add New FTE for Conversion", URLRoot() & "db/" & Dbid() & "?a=API_GenAddRecordForm" & "&_fid_53=" & URLEncode([Related Business case]) & "&_fid_129=60" & // Softcode the Months Needed to 60 FTE "&_fid_68=This Request is related to " & URLEncode([Request]) & "&_fid_123=14" & // Sets Request to "New FTE (Related Conversion)" "&_fid_127=FTE" & // New Employee Type "&_fid_84=" & URLEncode([Related Role]) & "&_fid_29=" & URLEncode([Related Level]) & "&_fid_38=" & URLEncode([Related Hiring Manager]) & "&_fid_43=" & URLEncode([New Dept1 #]) & // Dept #: sets field 195 to field F "&_fid_259=" & URLEncode([Record ID#]), "" ) )
Fomatting Date returned in Json Response
I followed the example listed here: How to use Pipelines to email a report at a specific time of day | Qrew Discussions (quickbase.com) However, my Json reponse includes a date. The example formats Percentage and Currency, but does anyone know the syntax need to format a date data? I need it in the MMDDYYYY format (no time stamp). Thank you. MarkWhat is the matter with my API Button formula?
Trying to create an API button to open a new record in another table (ideally will love to build this out while passing details on to specified fields. But. I can't even just get it to do a new record). What gives? I've compared this to some of my other similar records, and can't figure out why this won't work. Thanks!
API_GetUserInfo
Hello, The purpose of my pipeline is to dynamically add a user via API calls. The user who submits the request to add a "new" user has to input the "new" users email address. I understand that I then need to use that email address within the API_GetUserInfo to check if the user's email exists on any realm within Quickbase. If it does, then I should use the @id response data and insert it into API_AddUserToRole -> API_SendInvitation. If it doesn't exist, then I should use API_ProvisionUser -> API_SendInvitation. My issue is that if a user is not found within the API_GetUserInfo, it throws an error: "Quickbase reported an error: 2 : Invalid input : The user with the specified email address or username does not exist." I have tried adding an if statement to avoid the error and simply continue on: {% if b.json.qdbapi.user['@id'] != "" %} true {% endif %} However, it still throws the error if the user is not found. Is there any way to prevent this error from occurring? Thank you.
Save Before Navigating and API Edit Record Bug - Not bug...
I posted earlier about this and said I would update, but cannot find the original posting any more. I located what I felt was a bug, but Customer Service has stated is expected. This behavior may affect many of you, and I would be curious to know how many others have realized this is happening. When using SaveBeforeNavigating, if you have changed field values it is a random chance if the order will be: Save the Record and Grab the New Field Values or if it will be Grab Old Field Values then Save Record. Thus, you are are utilizing any changed fields (perhaps you are using an edit record api and taking the value of Field A, which was just changed), you will sometimes get the original value of Field A, and sometimes get the new value of field A. I guess both actions happen at the same time (grabbing the field values and saving the record), so it's a mini race to see which one happens first, and it switches back and forth. As they are labeling this as expected behavior, I suppose we will need to start a feedback if it is something we would like to see sequential (save then get field values). Wondering if others would be interested in this feature.
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. JamesQuickbase DBA
Hi, I have developed a project management application in Quickbase for my company. As our company continues to grow, more business units are being created, making it essential to integrate them into the application. This growth has highlighted the need to standardize our database. I am seeking guidance on Quickbase best practices for database administration. Any advice or resources would be greatly appreciated. Thank you.Saved Value is not registering before redirect
I just encountered an issue I have never seen and am wondering if anyone else has come across this. I have a Formula Rich Text Button that Does the following: 'Class=Save Before Navigating' Run an API_EditRecord and set a half dozen fields. I am in Table A, and there is a record in table B being edited. The problem I am having is I will see the 'Saving' dialogue come up (indicating my record is being saved), but it doesn't always see that field was changed. Here is an example. For example, I changed a singular text field (minimally, I removed a period). The auto save ran, but then it indicated '0 fields changed'. Yet, I can see on my launch record the field is in fact saved, without the period. A field definitely changed. (I would post a picture but that seems to be bugged) This is not consistent. Sometimes I run the test and the edit is made as expected. Another time I will run the test and it doesn't register the change. It is almost as if it is a race against the clock. Sometimes the EditRecord API is running before it can tell a change was saved. Has anyone else run into this?
