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.
automate role granting process - add admin to all apps
Hi guys. I am currently working on a project thats going to automate role granting process based on the requests in ServiceNow so I am looking to utilize the HTTP API to grant user a role through API_AddUserToRole. First I want to export current roles related to all active apps in Quickbase - a whooping 429 apps to be able to create a predefined drop-down (we are currently not creating more roles/apps). I understand that through API_UserRoles call I can get all roles associated with one app, so if it means that an account with admin access on all apps can generate list of all roles for all apps. How can I streamline granting such admin access to 429 apps? Or granting some access level to all apps? Any advice or strategies would be greatly appreciated.
Incompatible value error
I'm using the API to create records, from time to time I get an error that says incompatible value, today I got it again: "lineErrors" => { "7" => ["Incompatible value for field with ID \"43\".", "Incompatible value for field with ID \"93\"."] } This is the record in question: {"6"=>{:value=>blah}, "11"=>{:value=>"2024-04-16T07:59:30-05:00"}, "12"=>{:value=>"2024-04-16T14:50:00-05:00"}, "13"=>{:value=>"blah"}, "24"=>{:value=>blah}, "25"=>{:value=>blah}, "43"=>{:value=>21418}, "93"=>{:value=>269}, "15"=>{:value=>11356}} There are 3 more record that are created properly, those 3 records share the same values for 93. I also check the records for the value on column 43 and all those exists. It is driving me crazy. Any idea?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?