After upgrading to Pro 3.4 our attribute rules using the $datastore throw a 'Table not found' or a 'Layer not found' error. We're on AGE 11.1 and using branch versioning.
The error shows what looks like a GUID instead of the layer name.
I ended up creating a ticket.
Same here! It's only erroring out on one arcade expression even though everything looks fine. The table exists etc. and we use this same expression format for other rules that aren't erroring out.
Did you find a solution? I'm about to put in a ticket.
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
