Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :

How to avoid user data import errors using Business rules?

Arun Vinoth Profile Picture Arun Vinoth 11,615 Moderator
Recently our beloved end user exported all the records in Excel, but he just wanted a blank template to import, assuming he cleared the records entirely but he just cleaned the cell values. You know what the hidden columns for re-import feature after bulk edit were not visible for him (I know!)


Once he imported the Excel file.. boom! all the records were showing empty attribute values in Production. Very soon, in fact of split seconds - Production users started the chaos.

We all know that "Business required" field setting in customizations won't affect data import.

Sad part is all our validations were done on UI part ie. CRM form validation using javascript and nothing on Plugin side for Business logic validation. So the import went through all the way.

We were able to find out using the Audit & Organization Insights, then a huge data restoration exercise happened from everyday morning backup by DB restore.

Solution:
To avoid this in future we endup doing a simple trick of Business rule on Entity level.


The import will fail for create/update of records without required fields.



This was originally posted here.

Comments

*This post is locked for comments