Select to view content in your preferred language

Implement "Import XML Workspace Document" in Catalog Import instead of "Wizard"

91
2
yesterday
Status: Open
Labels (1)
SimonSchütte_ct
MVP Regular Contributor

As a user I would expect to be able to use the same menu workflow for exporting than for importing.
This is the case for all context menu options within the catalog for Geodatabases.
The only exception is the "Import XML Workspace Document Wizard".

In the catalog it is possible to use import and export tools via the context menu.
Examples: 

- Distributed Geodatabase -> Import Schema Changes -> "Import Replica Schema" tool

- Distributed Geodatabase -> Create Replica-> "Create Replica" tool
...

- Export -> Feature Classes to CAD -> "Export To CAD" tool
...
- Export -> Geodatabase To XML Workspace Document -> "Export XML Workspace Document" tool

- Import -> Feature Class(es) -> "Feature Class to Geodatabase" tool

- Import -> Table(s) -> "Table To Geodatabase" tool

- Import -> XML Workspace Document -> opens "Import XML Workspace Document Wizard" instead of "Import XML Workspace Document" tool, which would be expected.
The biggest issue is that the Wizard does not accept all XML files that are supported by the tool, notably xml files from replicas with "Register existing data only" option.

The current implementation is counter intuitive.

Users expect a Toolbox, not a "Wizard"
Re: Import XML Replica "Register existing data" - Esri Community

Proposed change:
directly reference "Import" with "Import XML Workspace Document" and migrate functionality from the wizard to the tool.

As an alternative: make sure the wizard has the same functionalities than the tool. At least provide appropriate error messages that explain to use the other tool.


Tags (1)
2 Comments
SSWoodward

Thanks for this post @SimonSchütte_ct 

This look like a bug with the Wizard.  I've opened an issue internally and will have the appropriate person evaluate a fix.

We Implemented the Import XML Wizard after multiple direct requests for this functionality as an ArcMap equivalency issue.  The consistent feedback we received was that users were expecting to access a Wizard, with rename capability, in this location.  

SimonSchütte_ct

Good to know, thanks.

Fixing the bug would be a great first step.

Moving the Wizard functionality into the toolbox would be logical.
Field Mapping/renaming capabilities already exist in other GP-Tools.

If we cannot get rid of the wizard, having an additional entry for the toolbox next to the wizard would be useful.