How does the Batch Update process work?

When does Core decide to send batch update to the 'offline' process, issue a notification and update the selected records? As an example, how does the Time and Expense Reviewer > Batch Update work when records are selected? How does Core determine the tolerance limit to send to offline batch processing and notification? 

There are some underlying rules for the Batch Update function in Core. There are some conventions or conditions being used for this process:

In case of Time Entries, Expense Entries and Reviewer screens,

  • If records selected are greater than 150
  • If you have chosen the Select All option
  • If you have selected more than 5000 records

...only a maximum of 5000 records gets updated at a time and you are notified when <n> number of entries or records get processed. After some time, you get new notifications to confirm that the batch update is completed for those <n> number of records.

  • If records selected are less than 150

... all the records get updated at a time and you see a wait cursor till the process is completed. You do not get any notifications. 

In case of other screens, all the records get updated at a time and you see a wait cursor till the process is completed. You do not get any notifications. 

Was this article helpful?
0 out of 0 found this helpful