Persistent attribute field calculation

[Ulises]

I noticed (or haven't found how) that field calculation in Enterprise is a one time action that do not persist having to run calculations again as needed.  I suggest there is a way to set calculations to be persistent in the table as a way to keep data updated and complete...like using attribute rules in AGOL or Enterprise.

Thanks

[Bud]

I believe attribute rules can be used in enterprise geodatabases.

Can you explain why attribute rules won’t work for you in ArcGIS Enterprise?

Related to calculated fields in general: 

• ArcGIS Pro Idea: Virtual Attributes (ad hoc)
• Create Database View (Data Management)
• Query layers
• Idea: Virtual SQL Attributes in ArcGIS Online
• Idea: Support for Attribute rules in ArcGIS Online
• Idea: Database views in ArcGIS Online (with exportable computed columns)

[Ulises]

Hi @Bud, 

Just realized my post was not clear so I apologized for the ambiguity.  Attribute rules work fine when defined in my geodatabase but can't be implemented in AGOL or Portal.  Thanks for the links; one of them referred to my post.

Regards

[Scott_Tansley]

You can do it in enterprise if you use a traditional feature service and enterprise geodatabase, but you’re right in saying AGOL and hosted services don’t support it.  🙂

[Bud]

@Scott_Tansley 

Side note:

Can Portal either use ArcGIS Enterprise (on-prem) or hosted services?

[Scott_Tansley]

It depends on the specific use-case you're exploring. 

Certainly 'Portal' can use a federated or stand-alone ArcGIS Server, with a Map Image Layer with the Feature Access capability turned on.   A hosted layer, where the data is stored in the relational data store has many advantages from performance through to ease.  Those advantages do not include attribute rules, which is why we set them in the Enterprise Geodatabase and expose them via the Feature Access option for editing from the web.  

You can do the same via Collaborations or referencing from AGOL as well, if you're in Hybrid mode.

There are some places in Portal, though, that may natively use the Hosting Model - and that's why it's use-case specific.