POST
|
There's an idea that roughly covers this topic that could do with some votes: https://c.na9.visual.force.com/apex/ideaView?id=08730000000btEU&mc=0 Although I may submit a new idea later that is a bit more comprehensive, once I've learnt a bit more...
... View more
02-11-2014
10:24 PM
|
0
|
0
|
761
|
POST
|
If you edit a feature in one version, and delete it in the other, the Conflicts dialog will let you choose which version to keep. So the functionality effectively already exists to intervene and stop a feature being deleted, it just needs to be extended to cover non-conflict changes. The logical place to put this would be in the Version Changes dialog. In the meantime, perhaps you can force a conflict by updating a single (redundant) attribute across all features in the target version. Then if a feature is deleted in the edit version it will be in conflict and allow you to review it. However you could end up having to click away at the Conflicts dialog quite a lot to review all the changes one by one (it's not possible to select multiple!).
... View more
02-11-2014
10:05 PM
|
0
|
0
|
761
|
POST
|
When I run the "Version Differences" tool from the Data Reviewer toolbar and write the results to the Reviewer table, am I then able to reject specific changes? Specifically, if somebody deletes the wrong feature in one version and then saves their edit, how do intercept this error before posting it to the DEFAULT version? I don't see any way of rejecting a delete with any of the Data Reviewer functionality, nor as part of the versioning reconcile / post process (especially since there are no conflicts). Maybe I'm missing something obvious here? Any help would be appreciated!
... View more
02-11-2014
05:24 AM
|
0
|
2
|
3464
|
POST
|
I have now tried the Data Reviewer extension, and this gives me a bit more functionality by allowing me to browse through the results of the "Version Differences" tool, and make amendments directly to these affected features in the main map view. In order to see any deletes between versions however, I need to write the results to the Reviewer Table. From here I don't see any way of rejecting a delete / resurrecting a feature that has been incorrectly deleted. So if somebody deletes the wrong feature in one version and saves their edit, how do intercept this error before posting it to the DEFAULT version?
... View more
02-11-2014
05:08 AM
|
0
|
0
|
761
|
POST
|
there is currently no tool or technique to combine the conflict detection manager and the version changes tools ... as the "power user" and the one with all the permissions, I can't simply accept or reject any edit. I still need to identify and check the edits using version changes and/or other tools (see next paragraph) and, if I find any problems, communicate them to the editor and get them corrected. I'm new to the whole versioning thing, but it seems to me that the QA person is severely limited by not being able to actually review (i.e. accept/reject/amend) edits whilst looking at the changes between versions. Is there a best practice approach for dealing with bad edits? - Or does the QA person have to visually check all the changes, make a note of any issues and then contact the person responsible? Rudy pointed me toward a free script in the Resource Center. I've found it stable, easy-to-use, and helpful (if not a 100% solution): "Show Edits Since Reconcile" at http://resources.arcgis.com/gallery/...C-60E304332809 I notice that this hasn't been updated for 10.1.
... View more
02-07-2014
04:52 AM
|
0
|
0
|
761
|
POST
|
Feature services do not support annotation feature classes Are there any plans to support this in future?
... View more
09-12-2013
05:29 AM
|
0
|
0
|
391
|