Is there a way to strip out attribute rules when exporting a feature class to a new file geodatabase?

[MatthewBeal]

I have a script that exports a feature class from geodatabase A to geodatabase B. Geodatabase A is our primary editing environment and the feature class has multiple attribute rules configured.

Geodatabase B frequently has ArcMap users that access it. No editing occurs on this database at all. It is strictly a view only database. The problem I am having is that exporting the feature class from A to B also brings across the attribute rules. Since ArcMap doesn't support attribute rules this just breaks the layer for those users until I manually go into the attribute rules for geodatabase B and disable them. Is there anyway to configure that export to not include attribute rules?

[DanPatterson]

Disable Attribute Rules (Data Management)—ArcGIS Pro | Documentation

does this work?

[MatthewBeal]

Unfortunately not. All that does is disable the rule. ArcMap cannot read a feature class if any attribute rule is present, even if it is disabled. 

[avonmoos]

This might not be the best approach but create a script that exports the data to .shp and then imports those into your other gdb.

[MatthewBeal]

I had tried that but it truncates the field names which can cause issues for the end users maps that are already configured to use the original non-truncated field. 

[DanPatterson]

field name length is a limitation of shapefiles

Geoprocessing considerations for shapefile output—ArcGIS Pro | Documentation

Field names cannot be longer than 10 characters.

[JayCary]

How about deleting the attribute rules in the exported feature/object classes (followed by deleting the error layers)?

Delete Attribute Rule (Data Management)