Attribute Rules won't execute on SDE feature dataset

Question

Good afternoon

My organisation has created a new enterprise geodatabase in SQL Server. We have created a data owner user for the new EGDB that was used to load various feature classes into the new database. During the data loading, several attribute rules were created on the new feature classes. These seem to execute as expected.

I have subsequently created a new data editor user on the EGDB that has all the required permissions to SELECT, INSERT, UPDATE, DELETE.

This new user generally seems to behave as expected. I am able to read/load the different feature datasets. However, when I try to create a new feature in any of the datasets that have an attribute rule applied I get an error message ("Failed to evaluate Arcade expression. [Rule name: Calculate Unique ID, Triggering event: Insert..."). I am not able to add any new features, although interestingly I am able to edit existing features within the feature classes with attribute rules.

Checking the attribute rule window, it gives a message that says "The table or feature class corresponding to this view is read-only". This doesn't seem correct as I am able to modify the feature class, I just can't add new features.

Furthermore within the new data editor user I am unable to add/edit/delete attribute rules. However, if I use the data loader user to remove the attribute rules, I am then able to create new features using the data editor rule.

In short it seems that only the data owner is able to create and execute attribute rules on feature classes. Other users with sufficient privileges are unable to create features within the feature classes if there is an attribute rule in place. The data editor is also unable to execute/edit/delete existing attribute rules.

Just wondering if this is expected behaviour? Is it possible to for attribute rules to be created and executed by a user other than the data owner.

Thanks for your consideration.

Peter_Green · Accepted Answer

So, in the end this wasn't an issue with the attribute rules, but with a database sequence I had created that the attribute rule was using as a counter. As far as I understand the database sequence sits as an object in the database, just like any table and needs the correct permissions to execute using a non-data owner user.

The simple solution was to include the name of the database sequence owner as part of the call to the database sequence in the attribute rule. The attribute rule ended up looking like this:

var id = NextSequenceValue("sequence_owner.sequence_name")
return id