Skip to content
Best Practice Recommendations
- Minimize number of fields: processing times vary and increase as the amount of data to access/update increases. Foreign key and lookup relationships may also extend processing time. While it is not always possible to reduce the number of data columns provided, consider optimizing the file size based on intended actions. For instance, you may wish to update the email address field of your employees. Rather than combining this update with the insertion of new employee records (that require the inclusion of more data fields), construct a file specific to the field to update.
- Optimize file size: Guardian does not restrict the number of files to be processed. As a result, organizations should build files specific to the results they are intended to achieve (e.g. update an employee record field), or break-up a large file to reduce its overall size.