Issues with Using Attribute rules to assign parcel number in the Parcel Fabric Service

[JoeGuziStarkCountyOH]

Greetings Esri Community,

     I hope this post finds you well and that everything is awesome. I'm desperate. I am trying to write a rule that will generate a parcel number and calculate the Name field of the parcel parcel type in the fabric. I created a geodatabase sequence, written the calculation rule as a batch calculation rule, so I can run it manually at the appropriate time via the evaluate rules gp tool, and I get the dreaded 999999 error. This rule works in a file geodatabase, and in a feature service with the just the parcel fc and the validation fcs in the service. Therefore I am confident that expression works. I get the error when I run the evaluate gp tool on the parcel fabric service. Here are the details:

• System
  • ArcGIS Pro 2.9.3, also tried 3.0
  • ArcGIS Enterprise 10.9.1
  • Windows Server 2019
  • SQL Server 2019
  • GDB Version 10.9.1.2.9
• Attribute Rule on the Parcel FC in the fabric
  • Calculation Rule
  • Execution: Exclude from application evaluation, Batch
  • It should be noted that when I initially created the rule, I did not check the Exclude from application evaluation box, but it would not allow me to save the rule unless I checked it...
    • Error:  Error 002920: Exclude from Application Evaluation Must be enabled [ while using sequences. (RuleName: name of the rule)]. Error 002556: Attribute rule not found.
    • When I check the Exclude from application evaluation box, that error goes away and I can save the rule.
  • Expression: return nextsequencevalue("ParcelNumberAssignmentSequence");
  • Field: Name
• Sequence:
  • sequence name: ParcelNumberAssignmentSequence
  • Start with: 10015314
  • Sequence increment value: 1
• Implementation:
  • The Parcel fabric was already published as a service.
  • after I implemented the rule I overwrote the service
  • added the service to a new map
• Parcel Fabric Service Settings
  • Service was published using the owner connetion
  • The owner connection is set to be Branch Versioned
  • all of the data in the service is Branch Versioned
  • The Parcel Fabric Service is a Feature Service
  • The Validation capability is checked
  • The Version Management capability is checked
  • The Parcel Fabric Capability is checked 
  • I have been able to edit the fabric through this service... everything about the service seems to be working fine
  • I just can't successfully run the Evaluate Rules GP Tool
• testing workflow
  • selected a parcel
  • ran the Evaluate Rules GP Tool
    • Input workspace: my parcel fabric feature service url
    • Evaluation Type: Calculation Rules
    • Extent Default
    • Async Checked
  • Error: ERROR 999999: Something unexpected caused the tool to fail. Contact Esri Technical Support (http://esriurl.com/support) to Report a Bug, and refer to the error help for potential solutions or workarounds. Unidentified Error Failed to execute (EvaluateRules)
• Troubleshooting:
  • I am able to run this tool with the same rule set up on a file gdb
  • I also published the parcel layer and the validation layers in a service by themselves, from the same fabric, and the tool ran successfully
  • Therefore, I am reasonably confident that the rule and expression are fine, the problem seems to be with the parcel fabric service and it's execution of the rule.  
  • When troubleshooting the parcel fabric service
    • I also tested on the default version, and a created version. 
    • I have tried specifying the parcel layer with in the feature server url
    • I have gotten the same error every way I have tried it

Ok I think that is everything. Thank you in advanced for any help you can provide. We're hoping to implement the pro parcel fabric in the upcoming weeks, and assigning parcel numbers is very important to our workflow. Thank you for everything and have a delightful day.

Sincerely,

Joe Guzi

[HusseinNasser2]

Hey Mike, if you use the Evaluate Rule gp tool and select the features you want to evaluate , the tool will only evaluate selected features. 

This isn't currently available when evaluating through error inspector 

[AmirBar-Maor]

@JoeGuziStarkCountyOH 

Assuming you checked the Validation capability when you published, you should be able to see the validation REST API exposed on your server:

The first thing I did was to verify that the Evaluation service REST API supports a selection set.

It does 🙂

To use the geoprocessing tool Evaluate Rules you will need to supply the 'Feature Server' URL of your published map. It will end with '...FeatureServer' and will look like this:

Also notice it is set to Calculation rules.

Now you can run it on a selection for the 'default extent' (all of the data).

To see the update (another 'gotcha'), you will have to select the version in the contents pane \ data source tab and then hit refresh. I have verified that only the selected features are updated.

However, getting a 999999 error is always a BUG.

[JoeGuziStarkCountyOH]

Greetings @AmirBar-Maor ,

      Thank you for your response, and for finally trying the actual workflow I originally posted about. You assume correctly. Please see the original post, the validation capability is checked. In fact, you have to have the Validation Capability Checked when you publish a parcel fabric service. It will not let you publish if that capability is not checked. You can also find from earlier posts and screenshots that I have had the Evaluate Rules GP tool set exactly how you have it. 

     I tested again following your screenshots. The 'Gotcha' you mentioned, was interesting. I made sure to do that this time. I ran the Evaluate Rules GP tool and got the same error. I have included a new screenshot showing the results. 

Thank you for everything and have a delightful day.

Sincerely,

Joe Guzi

[DrewDowling]

@HusseinNasser2Does this bug also potentially affect immediate attribute rules? I've had problems in the past getting rules to work when they are applied to a subtype. But the same rule works fine when applied to the whole feature class. Unfortunately it's inconsistent behavior and I can can't duplicate the issue consistantly.