Instead of writing input scripts from start-to-finish, you can export scripts from the database and create your input script by starting with, modifying the exported script.
Before you begin
You must have administrative permissions to run this program.
About this task
This approach is recommended if you want to:
- Use an exported script as a basis for creating similar declarations.
- Verify metadata declarations already made to the repository.
- Copy customer-specific metadata declarations between different environments.
Procedure
- Double-click the TriDK XML Setup executable $\AppCore\Utilities\TridkXMLSetup\Tools\TridkSetup.exe
A command line window displays with Valid applications listed. These are names that can be used in the next step.
- Specify the SDL LiveContent Architect application you want to modify (-App).
- Enter a valid username (-User). This value is case-sensitive.
- Enter the password for the user(-Pwd)This value is case-sensitive.
The TriDK XML Setup Tool logs into the application.
- Enter the value export for the -Action parameter.
- Provide the file name of the input script.
- Enter the file name of the completed script.
Give descriptive names to the output files, such as [xxx].export.xml.
Results
A completed script is generated.
Note:
- If the "exportmode" attribute equals "full" all definitions are exported recursively, excluding the actual values of an LOV. For example, for a card type this means that in addition to the definition of the card type, the definition of all fields (defined on that card type) and LOVs (attached to fields) are included in the generated completed script.
- If the "exportmode" attribute equals "cascade", all definitions are exported recursively such as in "full" mode, but all the values of the LOVs are also included.