Writing to a logged text field via API over a certain number of logged entries

Question

This question is more for solving my curiosity than it is a request for alternate solutions.&nbsp; I was using a formula rich text field functioning as a button to make an API_EditRecord call to update a logged text field.&nbsp; This worked well until the logged field accumulated more than 7 or 8 entries.&nbsp; Once the field exceeded that number of entries, the request resulting from the button click would sit in the queue pending for about 20 seconds before it finished executing and redirected.&nbsp; Does anyone happen to know why?&nbsp; As soon as I wiped the log clean and tried again, it would update and redirect almost immediately.&nbsp; Is there something weird about how the logged edit fields work?&nbsp; Thanks in advance if anyone has any idea how that functions.&nbsp;&nbsp;

evanmartinez · Answer

Hi Christine,Out of curiosity when you are writing the data over via the API_EditRecord and writing into the log edit field are those logs bringing over a large amount of data or only a few lines of text? I have worked with users in the past to update log edit fields from another entry field via Actions, Automations, and buttons and not run into this same slowdown but some imports/edits can be impacted by a large amount of data being passed or high traffic during the time the method was used.

archiveuser · Answer

Hi Evan,&nbsp;Thanks for the feedback.&nbsp; No, actually, it's 15 or less characters worth of updates each time.&nbsp; The slowdown only occurs after there are approximately 8 or more previously logged (15 char or less) entries.&nbsp; It's not a huge problem for me as the field I'm writing to is unlikely to have more than 2 or 3 logged entries.&nbsp; It just sparked my curiosity, and I wanted to run it down in the event we have to deal w/ this same issue with a heavily logged field.&nbsp;Thanks again!&nbsp;

evanmartinez · Answer

Hi Christine,That isn't usual behavior for a API_EditRecord to struggle that much moving data in the absence of a large amount of data or the process running into very heavy traffic in the application. I have set up similar buttons in the past to populate log edit fields and usually only run into that type of trouble when the data set gets very large. There is also the option to instead of logging changes en mass in a log edit field to instead use an Automation or button to add every change as a child record for when data sets get large. It is also very helpful for running any reporting off of logging changes to a field as each change is a record that can be filtered and searched via the normal tools.&nbsp;If you find this slow down is still happening when using that Edit thought I would suggest putting in a case with the Care team and they can get application access and reproduce it to see if they run into the same trouble and can identify what step of the process is causing that slowdown.&nbsp;You can put in a case when signed into Quick Base by clicking on the question mark icon that appears in the upper right hand corner and selecting Manage Support Cases or directly&nbsp;here.

archiveuser · Answer

Hi Evan - thank you so much for your response.&nbsp; I appreciate the feedback!&nbsp;&nbsp;

Forum Discussion

Writing to a logged text field via API over a certain number of logged entries

Related Content

Extract Date and Comment from prepend log entry field

Filter Table Entries In Another Table

[Snippet] How we Stop Backdating Entries from user

Writing conditional logic on Pipelines trigger on new event step

Pipeline to write to Google Spreadsheet triggered by spreadsheet import