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

Hi Evan, 

Thanks for the feedback.  No, actually, it's 15 or less characters worth of updates each time.  The slowdown only occurs after there are approximately 8 or more previously logged (15 char or less) entries.  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.  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. 

Thanks again! 

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. 

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. 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 here.

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