I have a traditional versioned dataset that is not moving edits to base. "Department A" staff are editing this table with the SDE.DEFAULT version and do not have their own version for editing. It seems that staff are not always reconciling and posting their edits when they are complete. Therefore these edits don't show up in the base table and only in the versioned view table (*_EVW).
We have a nightly compression script that reconciles and posts versions. However, we had to recently modify this script to only reconcile and post one version that "Department B" is using. After modifying this script, I have noticed that the edits from "Department A" are not getting posted to the base tables.
Is there a way that I reconcile and post the SDE.DEFAULT version so that the edits "Department A" make will always get posted to the base table after the compression/reconcile/post script runs?
Would the code below work for this?
arcpy.management.ReconcileVersions("A:\Path\to\gdb",
"ALL_VERSIONS",
"sde.DEFAULT",
"SDE.DEFAULT",
"LOCK_ACQUIRED",
"NO_ABORT",
"BY_OBJECT",
"FAVOR_TARGET_VERSION",
"POST",
"KEEP_VERSION",
"c:/temp/reconcilelog.txt")
Thanks,
Josh
If users are editing in the DEFAULT version, you should not have to do a reconcile / post. All the edits would be in that version by default (maybe not in the base table). The compress "should" move the edits to the base table if there is not a blocking version (which there may be based on your information above).
You would need to reconcile the other versions to get them at the same state before the compress. That should allow the edits to move to the base table.
For that tool you mention above, look at the following option: