POST
|
Thanks Michael. I thought I had tried that prior to the post, but I guess I still had something incorrect in the parameters. We're trying to use this method to update field edits to the related table. We've gone this route because editing related tables isn't available in AGO. We were hoping that the field edits through collector/AGO would populate the feature class and then trigger the UPDATE_LINKED_RECORD method based on this set up. So far, it appears that the edits are coming through collector/AGO to the feature class, but those edits aren't being transferred via the AA rule we have set up. I have tried the rule just in the ArcMap environment and the rule appears to be working great. Do you know if this workflow is possible with AA? Simply, we're trying to go: Field Edits (Collector/AGO) -> Feature Class -> UPDATE_LINKED_RECORD -> Related Table.
... View more
08-08-2016
12:22 PM
|
0
|
1
|
837
|
POST
|
PUKSIGNID is the primary key in TrafficSignsFeatureClass and PKSIGN_ID is the primary key in the Maintenance Record table. The feature class, table, and dynamic value table are all located within the same enterprise geodatabase. The table is participating in a 1:1 relationship class with the feature class based on the primary keys identified above. Below is a snapshot of the dynamic value table showing the 2 rules I'm having issues with. I appreciate all your help.
... View more
08-05-2016
01:15 PM
|
0
|
3
|
837
|
POST
|
Michael - I am working on a project for a city and we are creating multiple apps for city and public works departments. We use AA quite extensively, but I'm having issues with UPDATE_LINKED_RECORD. I have a feature class, TrafficSignsFeatureClass, and a related table, TrafficSigns_MaintenanceRecord, participating in the method. I'm trying to update the related table when either of two status fields are changed in the feature class. I'm getting an error that says "ID OR FIELD TO COPY WAS NOT FOUND" in the log file, but the fields exist. I'll also get a message that says "Target value did not change, skipping" occassionally when I know the value has changed. Am I missing something simple? I've had odd issues with these particular fields before, ie domains won't be enforced in ArcMap but are enforced in AGO, so I'm wondering if there is something wrong with those individual fields. This is the first method in AA that has given me fits thus far, so for the most part the tool has run correctly. The methods page from ESRI is very helpful. I have attached the log file for a trial run of 3 records, so hopefully you can shed some light on my issue. Thanks Steve
... View more
08-05-2016
08:07 AM
|
0
|
5
|
837
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:25 AM
|