Latest Contributions by Sean_Haile

Garmin GLO is on the list and is a small bluetooth receiver. I wouldn't necessarily call that a "high accuracy" device, but it would likely be comparable to an internal GNSS receiver found in a tablet.  ... View more

I'm now trying to update the the service's JSON's formInfo section via ArcGIS Python API, I've determine how to retrieve the information, but not clear how to update it. It's not a part of the layer definition, so using that method doesn't seem to be appropriate. ... View more

Thanks for the reply. Yes, I can now see that in the JSON when using the AGOL Assistant. I didn't see that section when looking at the layer definition JSON from the Admin REST endpoint of the service, which is where I was previously looking. I've used both AGOL Assistant and the hosted layer's Admin REST endpoint's /updateDefinition capability to update layer definitions on hosted services, so I wonder why the JSON representation is different between AGOL Assistant and the service's Admin REST endpoint?  ... View more

Yes, our dataset is also branch versioned enabled, enterprise geodatabase 10.8.1 (sql server). Portal 10.9.1, editing occurs in Pro 2.9.5, using a feature service connection, editing a named version not default. The related record is in a table, related to a parent feature class. Primary/foreign key is a GUID field. If you'd like to share your attribute rule, I might have some suggestions. Not an expert, but do have this working for me in our environment. Sean ... View more

Hi @RalfSchmidt , We are adding the new related records via "Add New to Relationship". Using Pro 2.9.5. I think the important step to using either "Add New to Relationship" or "Add Selected to Relationship" is to have the attribute rule be triggered on UPDATE, DELETE, which is how my example above is configured.  When you "Add New.." it seems like the behavior is it first adds the new row to the related table, then populates the foreign key value from the parent, which is treated like an UPDATE rather than an INSERT. If the rule is triggered on INSERT then the foreign key isn't yet populated, so it wouldn't find a corresponding record in the parent feature to update during execution of the attribute rule. If you used "Add Selected..." you'd be in the same situation, the record's foreign key is being assigned during an UPDATE action, so you want the attribute rule to fire off then, so that it can find its corresponding parent feature to update. I also have "Exclude from application evaluation" checked, I don't know if that has any effect on this workflow, but thought I'd mention it here. ... View more

Yes, the attribute rule (assigned to the related table) is triggered when the related record is initially inserted into the related table and the row is assigned its foreign key value from the parent feature. I set the attribute trigger to UPDATE, DELETE because I think on the initial insert of the related record it doesn't yet have the foreign key value assigned to the record. ... View more

It seems currently possible to apply the calculation attribute rule to the related table itself (triggered during insert/update/delete), which could then execute calculations back on the parent table. In the example below, the calculation rule is applied to the related table, and when there is an action performed on a record in the related table, its parent feature's validation status is automatically updated. /* Attribute Rule Name: Calculate Parent Feature Validation Description: * Sets validationRequired on parent feature when a related table row is modified or deleted Subtype: All Field: TRT_GUID //need to use a field otherwise it doesn't save Editable: true Error Number: 600 Error Message: Calc Parent Validation Failed Triggers: UPDATE, DELETE Exclude from client app eval: true */ var trtGuid = $feature.TRT_GUID var fs = Filter((FeatureSetByName($datastore, 'TreatmentPT', ['GlobalID', 'TRT_GUID'], false)),'TRT_GUID = @trtGuid') var f = First(fs) if (f == null) { return trtGuid } //update className below to match fs name above return { 'validationRequired': [ { 'className':"TreatmentPT", 'globalIDs': [f.GlobalID] } ] } But if you wanted to make changes to attributes in the parent feature instead, you could return them in the dictionary as an "edit" to the parent as shown in this example:  https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/attribute-rule-dictionary-keywords.htm#ESRI_SECTION1_98D8C1A03B0D4BAB810DCC76DBA88F2C I'm successfully using this strategy now to update parent validation status, haven't fully tested it out but seems to be working as I describe. ... View more

Even if it is shared with Everyone in the organization, unless it is publicly shared a user needs to authenticate to AGOL (or have credentials stored with the item) in order to access the item. ... View more

I think it's because the base maps being used are AGOL base maps, and you would need to store login credentials with the corresponding base map item in your portal, or else the user will be prompted to also login to AGOL before the base map can be downloaded. ... View more

Not exactly, but there is a copy feature (attributes, shape, or both) function available when the previously entered feature is selected on screen, which can then "repeat" attributes and/or geometry in a second feature.    ... View more

You can set up your geodatabase to use contingent values: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/contingent-values.htm   ... View more

They are definitely honored in field maps when published using a federated server, I assume they would also honored by Field Maps when using hosted services in AGOL. ... View more