@ChaimSchwartzIroads
As you have found out, Attribute Rules constraints do precisely what their name suggests 🙂
Here are a few options to explore:
1. If you use editor tracking, you can use the creation time to skip checking the feature if it has been created in the last few seconds. Here is a code sample you might adjust for a similar case:
//Setting: If your data was migrated on June 18th 2019, you should add 2 days (June 20th) to avoid time rounding issue.
var MigrationDate = Date(2019,05,20); //Note: the month count starts at zero. year 2019, month of JUNE, 20th day.
var CreationDate = Date($feature.Create_Date);
if (DateDiff(CreationDate, MigrationDate, 'days') > 0){
return !IsEmpty($feature.CreatedByRecord);
}
return true;
2. You can set the default value of the field to a value and use the Arcade logic to ignore that value. That is not that good though, as there's no difference between this value and 'NULL'
3. Switch the rule to Validation Rule instead of the constraint rule. In many editing workflows features exist in an interim state, before they get planarized, merged etc. So it is easy to catch errors upon validation versus creation.
4. Use Task verification. It is not stored in the information model. The caveat is that the user must use the task. Any edits outside of a task will not be captured.
