Import Message (Data Management) (ArcInfo and ArcEditor only) |
|
Release 9.2
Last modified November 29, 2010 |
![]() ![]() ![]() Print all topics in : "Tools" |
Imports changes from a delta file to a replica geodatabase
Learn more about synchronizing disconnected replicas
Usage tips
This tool is only applicable when using replication in disconnected mode.
Accepts either acknowledgement messages or data change messages.
After importing a data change message you have the option to immediately export an acknowledgement message.
The following environment settings affect this tool: workspace, scratch workspace, and Configuration keyword.
Command line syntax
An overview of the Command Line window
ImportMessage_management <in_geodatabase> <source_delta_file> {out_acknowledgement_file} {MANUAL | IN_FAVOR_OF_DATABASE| IN_FAVOR_OF_IMPORTED_CHANGES} <BY_OBJECT | BY_ATTRIBUTE> {reconcile_with_parent_version}
Parameter | Explanation | Data Type |
<in_geodatabase> |
Specifies the replica geodatabase to receive the imported message. The geodatabase may be local or remote. |
Workspace | GeoDataServer|GPComposite type |
<source_delta_file> |
Specifies the file from which the message will be imported from. |
Workspace | File |
{out_acknowledgement_file} |
When importing data changes, this allows you to optionally export a message to acknowledge the import of a data change message. This option is ignored for anything other than a data change message. |
File |
{MANUAL | IN_FAVOR_OF_DATABASE| IN_FAVOR_OF_IMPORTED_CHANGES} |
Specifies how conflicts are resolved when they are encountered while importing a data change message. MANUAL — manually resolve conflicts in the versioning reconcile environment. IN_FAVOR_OF_DATABASE — conflicts automatically resolve in favor of the database receiving the changes. IN_FAVOR_OF_IMPORTED_CHANGES — conflicts automatically resolve in favor of the imported changes. |
String |
<BY_OBJECT | BY_ATTRIBUTE> |
Specifies how you would like to define conflicts: By Object or By Attribute. Defining conflicts by object will detect conflicts by row while defining them by attribute detects conflicts by column. |
String |
{reconcile_with_parent_version} |
Indicates whether to automatically reconcile once data changes are sent to the parent replica if there are no conflicts present. This option is only available for check out/check in replicas.
|
Boolean |
ImportMessage "Database Connections\Connection to workspace.sde" c:\data\housing.mdb TRUE IN_FAVOR_OF_IMPORTED_CHANGES
Scripting syntax
About getting started with writing geoprocessing scripts
ImportMessage_management (in_geodatabase, source_delta_file, out_acknowledgement_file, conflict_policy, conflict_definition, reconcile_with_parent_version)
Parameter | Explanation | Data Type |
in_geodatabase (Required) |
Specifies the replica geodatabase to receive the imported message. The geodatabase may be local or remote. |
Workspace | GeoDataServer|GPComposite type |
source_delta_file (Required) |
Specifies the file from which the message will be imported from. |
Workspace | File |
out_acknowledgement_file (Optional) |
When importing data changes, this allows you to optionally export a message to acknowledge the import of a data change message. This option is ignored for anything other than a data change message. |
File |
conflict_policy (Optional) |
Specifies how conflicts are resolved when they are encountered while importing a data change message. MANUAL — manually resolve conflicts in the versioning reconcile environment. IN_FAVOR_OF_DATABASE — conflicts automatically resolve in favor of the database receiving the changes. IN_FAVOR_OF_IMPORTED_CHANGES — conflicts automatically resolve in favor of the imported changes. |
String |
conflict_definition (Required) |
Specifies how you would like to define conflicts: By Object or By Attribute. Defining conflicts by object will detect conflicts by row while defining them by attribute detects conflicts by column. |
String |
reconcile_with_parent_version (Optional) |
Indicates whether to automatically reconcile once data changes are sent to the parent replica if there are no conflicts present. This option is only available for check out/check in replicas.
|
Boolean |
# Create the Geoprocessor object import arcgisscripting, sys, scripting, os gp = arcgisscripting.create() # Set the necessary product code gp.SetProduct("ArcInfo") # Load required toolboxes... gp.AddToolbox("Data Management Tools.tbx") # Process: Import Message... gp.ImportMessage_management("Database Connections\Connection to workspace.sde", c:\data\housing.mdb, "TRUE", "IN_FAVOR_OF_IMPORTED_CHANGES")