Legacy Data - How to handle in UN

[TJ_Houle]

Hi everyone-

We are migrating a pretty large gas data set to the UN. We have a situation where we have certain legacy data that is a part of the existing GIS, but we don't want it to necessarily have the same rules as newer data?

For a quick example, an existing plastic to plastic connection is valid, but we don't want users to be able to add a new one.

Does anyone have ideas on how we could implement this? 

• Lifecycle status?
• Minimal connectivity rules with very explicit attribute rules?

Any thoughts or pervious experience would be very helpful!!

[MikeMillerGIS]

Best option is an attribute rule to restrict the edit. This rule would be disabled when the data is loaded and then enabled once editing has started.
I do not have a rules that meets your needs prebuild, but an example of a constraint here can be found here:
https://github.com/Esri/arcade-expressions/blob/master/attribute_rule_constraint/only_at_start_end.m...