Support for Attribute rules in ArcGIS Online

[Yann-EricBoyeau]

At pro 2.4 ESRI implemented attributes rules at the file Geodatabase Level which is great.

It means that when you copy or move the file geodatabase, you copy or move the rules.

So if you upload this fgdb to AGOL, the rules are uploaded within the fgbd. 

Attribute rules are « able to travel » to AGOL.

At the moment these rules are not interpreted or implemented at the AGOL level.

The idea here is to have the rules interpreted and implemented in AGOL when publishing feature services from a rules enabled fgdb.

It would be great to have attributes rules fully implemented in ArcGIS Online.

This would allow users to have their own QC and field calculation in hosted feature layers and web apps !

(edited 2020-07-24 to improve this description)

[LouieRowley1]

Must have, the sooner the better.

[GISUSER6]

Please get attribute rules capable of being applied to feature services. Our systems primarily rely on Attribute Assistant but with the push to move completely to ArcGIS Pro and Attribute Rules, the process we would have to currently use seems like a step backwards from just sticking with ArcMap and Attribute Assistant if the rules are not applicable to ArcGIS Online. In 2026 we will have to start paying double for ArcGIS Pro Annual license from what we do now for ArcGIS Desktop and we won't have the same functionality with Attribute Assistant. It feels like even another step backwards because we will be expected to pay more for a product that doesn't offer the same funcitionality. 

[AndrewM-CTRWinchell_FAA]

@KellyGerrow has there been any update to if/when attribute rules will be supported in AGOL? It seems like they have already been in Enterprise for at least 4 years, how come it hasn't made its way into AGOL?

[CharlesWeise1]

We met with several product leaders at UC2023 last year.  The ability to publish attribute rules to AGOL would require a great level of organizational collaboration and a few high level executive decisions.  If you notice, the attribute rules are a different section of the ArcPro interface - so, programmatically, when publishing - the object attribute generated and sent to AGO servers do not include the attribute rules.  But, they do include the domain definitions (one-way).  So, we pitched the concept of adding another attribute to the object that is used to publish to the AGOL service.  The room fell to a cricket level.

So, we've adopted and are building out capabilities with FME.  If anyone reading this is a part of an organization that is interested in learning more, we love to share.  cweise@bowman.com.

[D_AnneHammond]

So what's happening here is that ArcPro and AGOL diverge on this capability (like so many other capabilities) but these two interfaces are supposed to be compatible.  I'm so frustrated being promised, or seeing advertised, functionalities that are not possibilities! 

[QuantitativeFuturist]

@CharlesWeise1 "organizational collaboration and a few high level executive decisions". This is exactly the problem and it appears that internal organizational collaboration is absolutely not happening and there is nobody making smart high level executive decisions. Surely someone is looking at the software holistically and ensuring consistency and interoperability? 🤣

[N8-CORR]

@MarianneFarretta Is Esri working on this or considering this? An update in this thread would be extremely helpful.