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)

MikeSlattery

Hi ESRI folks and community,

tl;dr - esri please update us and/or point us to deployable notebook examples for some of these problems if that's the realistic endgame.

I've added use cases and comments to this thread in 2019, 2020, and 2021. The last response from an ESRI employee was years ago I think. I have been out of the loop but sadly the apps I was maintaining found other solutions elsewhere. I might have some new use cases, but this item is still outstanding, as is the contingent values issue, and auto incrementing and they all seem related.

It is amazing to be able to put tools in people's hands as quickly as AGOL+Field Maps allow, but stuff like simple key/value additions for entry forms sometimes means starting over, which feels wrong.

I got a PC just to manage domain values via Pro. Last time I checked I can't maintain them easily without keeping up that PC for the ESRI suite. IIRC running notebooks against these was hit-or-miss. Where I'm at, AGOL looks like the default environment for everyone who needs to manage one or two important projects per decade, but that is a good number of people here.

I will look into throwing notebooks at some of the problems but I would still need to mark records as dirty until the notebook runs. Maybe some solid notebook templates would go a long way to help with domain key/value pairs, contingent values, etc.

Apologies if there are solutions that have cropped up in RTM territory. All clues welcome. I'm going to be unfair and send shout outs to some ESRI folks who have participated in other ideas threads, to ask if there is anyone over there who can tell us more about status: @bbollin @EmilyGeo @RussRoberts

Bud

For anyone who’s interested, it sounds like we can add calculated expression fields to “advanced views” in AGOL via the Admin REST API. The view would be uneditable. And this only seems to work for views with joins.

Add to Definition (Feature Service)

"sourceLayerFields": [
  {
    "name": "zipcode",
    "source": "zipcode"
  },
  {
    "name": "salesavg",
    "alias": "SaleAveragePerCustomer",
    "expression": "(Total_Sales_FY13 + Total_Sales_FY14) / Customers",
    "type": "esriFieldTypeDouble"
  }
]

Abdillahi Hassan shows it in a video on LinkedIn:
https://www.linkedin.com/posts/abdillahi-hassan-56a020134_esri-arcgis-ugcPost-7360636518803152896-Nn...

That’s not the same as attribute rules. But is related.

Ideas: