Cannot Test Attribute Rules on Branch Versioned Utility Network Data

[LeviCecil]

So I'm trying to create attribute rules for Branch Versioned Utility Network Data. I have a Structure Junctions dataset with two related standalone tables for Power Pole and related assets inspections. I'm trying to create rules that change the symbology of the SJ feature data based on whether a report has been submitted for that asset in Field Maps. I cannot test these without publishing the entire UN network to the Portal. Everything on the sde is locked in Pro. I'm unable to troubleshoot if a rule doesn't work in Field Maps, there are no errors, it just doesn't work. I tried bringing the published Portal data back into Pro, but I wasn't able to do anything with that either. Does anyone have any advice on how I can test these attribute rules BEFORE I publish??

[HusseinNasser2]

The easiest way to test attribute rules is on a mobile geodatabase. You can create mobilegdb, add the classes and attribute rules, do the edit in Pro and verify the rules work. Once you are sure, export the rules and import them to your enterprise geodatabase. 

I wrote a simple Attribute rule to demonstrate what you are trying to do. When the pole has no inspections record the symbology is grayed out, when we add an inspection record, it turns red. I'm essentially maintaining an attribute on the pole called inspectioncount, for every related record added, removed, the count is calculated and the pole is updated. 

Hope that helps (attached)