FAQs
This section contains a list of frequently asked questions on WorkZone Export/Importfunctionality. Click any question below to see the answer.
After import, some of my configuration items from the export file are not updated or created, and I see messages about a transaction limit in the console. What does it mean?
If the number of changes exceeds the limit that is set up in WorkZone Export/Import and WorkZone Content Server, you will receive a message in the console that advises you to either keep repeating the import command until you get a successful result, or to use a different import strategy.
See Session logging.
When I've run the import command, some of the changes that should update existing configuration items are not imported. At the same time, I don't see any error messages. Why is that?
Sometimes, an entity doesn’t have a unique property other than its ID, which is controlled by WorkZone Content Server. In such situations, WorkZone Export/Import uses the default logic to identify the item to update by the item's ID, which is often different from the ID in the export file that you used to create the item. The default scenario to follow in such cases is as follows:
-
The entity is created by import. The ID values in the export file are ignored as WorkZone Content Server will assign new ones.
-
You want to update the entity by running a new import command.
-
A new export file is created with the export command, and this file contains the valid ID properties assigned by WorkZone Content Server.
-
You can make the desired changes in the new file manually.
-
An import command is run with the new file and changes will be implemented according to the valid ID properties.
Can I include multiple entities with the --partialConfiguration attribute?
Yes. For example: --partialConfiguration "WzpSettings, WzpSystemPrintTypes".