I have a Constraint Attribute Rule that was working with ArcGIS Pro 2.9.2 and ArcGIS enterprise 10.9. After upgrading to 10.9.1 the attribute fails attempting to save edits when editing a through a feature service. The attribute rule is applied to an un-versioned enterprise database table. It seems that it will pass the client validation but fails on the server because the getUser.groups is empty. The attribute uses the GetUser as modeled in the video getUser.
var p = Portal('https://xxxx.localdomain.com/portal')
var user = getUser(p);
var groups = user.groups;
if (Find("Survey",groups) > 0) {
return true;
}
return false;
Does this seem like expected behavior?
