topic Re: DBMS Sequence not found when using Attribute Rules in ArcGIS Pro Questions

DBMS Sequence not found when using Attribute Rules

CraigCarsley — Fri, 22 May 2020 21:04:06 GMT

I set up an attribute rule to populate a unique ID field in our Address Points layer.

I also set up a corresponding database sequence.

When I add an address point as the database owner, no problem.

When another user who is not the database owner adds an address point, they get an error message about the database sequence.

Anyone have any idea what could be causing this?

Re: DBMS Sequence not found when using Attribute Rules

JoeBorgione — Fri, 22 May 2020 21:11:34 GMT

Stating the obvious, it must be a permissions issue. Can a non database owner create a sequence? Did you create it with the tool or with arcpy? I've only created sequences in file geodatabases but would like to deploy them at an enterprise level eventually, so this is of great interest to me.

Re: DBMS Sequence not found when using Attribute Rules

CraigCarsley — Tue, 26 May 2020 20:33:07 GMT

Joe Borgione‌ - That was my first thought as well. We even tried enabling a non-database owner user with the same privileges as the database owner, but still no luck. Only the database owner (which was also the creator of the db sequence) can run this particular attribute rule.

I created the database sequence with the tool.

Re: DBMS Sequence not found when using Attribute Rules

JoeBorgione — Tue, 26 May 2020 20:39:55 GMT

Is this part of your deployment of the Address Data Management solution by chance?

Re: DBMS Sequence not found when using Attribute Rules

JoshSaad — Tue, 26 May 2020 20:54:58 GMT

It looks like it can't find the database sequence that's referenced in the attribute rule. Can you check the sequence name spelling in the rule, or verify that the sequence exists in the database? Create Database Sequence—Data Management toolbox | Documentation

Re: DBMS Sequence not found when using Attribute Rules

CraigCarsley — Tue, 02 Jun 2020 21:22:35 GMT

Thanks for the reply. I would normally agree with you, except that the rule does work when its executed by the data owner, but not any other users. If the issue were sequence spelling, or if the sequence didn't exist, it wouldn't work at all- no matter what user.

Re: DBMS Sequence not found when using Attribute Rules

CraigCarsley — Tue, 02 Jun 2020 21:24:37 GMT

Joe Borgione‌ - Not exactly, no. We created our Address Points using the ArcGIS LGIM about 8 years ago, and we have maintained it, separately, since then. We've used Attribute Assistant all this time, but I'm trying to move us over to using Attribute Rules. All rules were created custom by me, not as part of a solution.

Re: DBMS Sequence not found when using Attribute Rules

JoeBorgione — Tue, 02 Jun 2020 22:11:13 GMT

I hate saying this just because of the pain you'll endure, but it may be time to give Tech Support a call...

Re: DBMS Sequence not found when using Attribute Rules

BThompson — Tue, 23 Jun 2020 21:13:43 GMT

Craig Carsley‌ I just ran into the exact same issue when setting up an immediate calculation rule to populate an ID field with a database sequence. I was able to resolve by fully qualifying the sequence name with the object owner. The Arcade expression should look like: NextSequenceValue('OWNER.SEQUENCE_NAME')

Re: DBMS Sequence not found when using Attribute Rules

Mandalorian — Tue, 18 Aug 2020 17:28:03 GMT

Craig Carsley‌ We ran into the same error in my organization as well with a calculation rule configured to generate a UID on INSERT. Interestingly, we also did the same thing as B Thompson‌ to correct the issue. Our Arcade Expression follows this syntax: return nextSequenceValue("OWNER.SEQUENCE_NAME")

Re: DBMS Sequence not found when using Attribute Rules

JoeBorgione — Wed, 16 Sep 2020 21:56:11 GMT

This is one of the irritations I have with Arcade and Attribute rules. There are some inconsistencies with them. I don't have to use the Owner.Sequence reference for my EGDB sequences like you guys are:

Re: DBMS Sequence not found when using Attribute Rules

Allison_Hockey — Mon, 26 Oct 2020 15:57:34 GMT

Here's an interesting thought too: I published my geodatabase to AGOL, and all the GIS techs access this data through portal. We do not have enterprise. I published to AGOL only, and we all access this data through portal. I built up the database sequences and when I bring the data in to my map through portal, non of the features create unique ID's any more. This is excessively frustrating, as I've built all of my relationship classes with these UID's. What can be done about this?

Re: DBMS Sequence not found when using Attribute Rules

JoeBorgione — Mon, 26 Oct 2020 16:08:25 GMT

Allison Hockey‌ - you might want to start a new thread.

I'm a little confused when you say that you access the data through portal but that you do not have enterprise. There is a way to publish a feature layer from an enterprise geodatabase such that the attribute rules will fire.

Re: DBMS Sequence not found when using Attribute Rules

Allison_Hockey — Wed, 28 Oct 2020 15:41:26 GMT

Hi Joe,

Our company has an ArcGIS Online for Organizations set up. We don't have enterprise. We are a few GIS techs spread across the country who gain access to the data that I publish to arcgis online from ArcPro and a local GDb.
The users then access that hosted data from arcgis online through the portal. I had set up database sequences and attribute rules in my local GDB before I published it and when I access the data from arcgis online, the DB sequences are no longer there and the attribute rules do not apply. My UID's no longer populate automatically. Perhaps this discussion is better in a different thread?

Re: DBMS Sequence not found when using Attribute Rules

JoeBorgione — Tue, 22 Jun 2021 08:26:44 GMT

see: https://community.esri.com/ideas/16977

Xander Bakker‌; Attribute rules can't be applied to AGOL hosted feature layers, can they?

Re: DBMS Sequence not found when using Attribute Rules

XanderBakker — Wed, 28 Oct 2020 19:21:05 GMT

Hi jborgion ,

Unfortunately, that is correct. Attribute Rules live on the data side and the relational datastore of AGOL is not yet supported.

Re: DBMS Sequence not found when using Attribute Rules

Raj-Chavada — Mon, 22 Mar 2021 16:58:42 GMT

@BThompson We had the exact same issue and it was resolved by using data owner account (prefix) as you highlighted in your post above. I wonder why your post is not marked solution by @CraigCarsley ?

Re: DBMS Sequence not found when using Attribute Rules

StefanDieters1 — Thu, 15 Jul 2021 04:10:16 GMT

I had what looked like the same problem. It seemed to depend upon the version of Pro. Calculation rule using NextSequenceValue worked fine with Pro 2.6, but not with Pro 2.8 Same rules, same Pro project, same enterprise database set up for branched versioning, same operating system. I initially thought it was because Pro2.8 need User.SeqName but the real problem was that Under Pro2.8 a rule using NextSequenceValue must have "Eclude from Application execution checked. This is enforced when editing the rule, but just throws an unhelpful error under Pro2.8.

Re: DBMS Sequence not found when using Attribute Rules

DNVT — Wed, 08 Nov 2023 20:16:18 GMT

@CraigCarsley Were you ever able to get around the owner issue? We use Enterprise Geodatabase with 3 sets of owners (ADMIN, EDITOR - read/write, USER - read). I can use the NextSequenceValue('OWNER.SEQUENCE_NAME') if I am the owner (ADMIN), but we publish our data for editing with the EDITOR user. If published through EDITOR, I continue to receive the "DBMS sequence not found." when inserting a new record.

Re: DBMS Sequence not found when using Attribute Rules

MarietteShin — Wed, 29 Nov 2023 17:28:53 GMT

Hi there,

I'm running into the same issue, but need a solution that works for multiple user edit versions at the same time against an enterprise geodatabase. Do you know if the solution you posted works for multiple users edit versions editing/accessing the feature attribute rule at the same time? Right now, it seems that only the schema owner has the permissions to use the Immediate Calculation rule with NextSequenceValue function.

Thanks.