Hello,
We have a process that uses the nifty Import feature (very helpful, BTW!). During testing, if a user uploaded a record with a blank field value that wasn't previously blank... like an OrderId... the Import feature allowed it and deleted the OrderId from the associated record. The field is required via CRM settings, but the Import process doesn't seem to validate against that?
I'm old school where we appropriately added value requirements at the database level, relationships, etc. Is it possible/within best practice to still do this (like in this case) and change the allow NULL setting at the database level in the CRM database? If so, if the Import finds an error, can it roll it back all of the changes like it would within a transaction?
Thanks for your help!
T