POST
|
Hello, We would like to use the attribute assistant to aid in editor tracking. I created rules using the Timestamp and Map Info to capture the date and version name that is being used for editing. I would like this rule to be triggered when new features are created, and also when existing features are modified, such as geometry or attribute changes. This does work, but not quite the way I need it to. We are editing features that participate in a geometric network, and if we create a new feature and connect it to an existing feature, the existing feature also has the date and version name updated. We don't want that. Does anyone know of a way to only have AA change attributes for features that have been directly edited, not just connected to features that have been modified? Thanks!
... View more
09-16-2019
10:27 AM
|
0
|
0
|
334
|
POST
|
Hi Kory, I recently installed 10.7.1 and I still get this same error.
... View more
09-04-2019
11:30 AM
|
0
|
0
|
1453
|
POST
|
Hello, I'm trying to set up the Reviewer workspace in our existing enterprise geodatabase. I'm looking through the documentation for storing the reviewer workspace in a geodatabase in SQL Server, and I'm wondering if I need to complete all of the steps outlined in ESRI's guidebook and the white paper that was published in 2013. I'm specifically wondering about creating the data files for the reviewer workspace. Is it really necessary to create FileGroups to store the Reviewer features and tables? Also, does the DBTUNE file need to be modified if we are using our existing production database as our Reviewer workspace? Thanks for any help in advance!
... View more
03-21-2019
10:35 AM
|
0
|
0
|
476
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|