integrity fetchviewset
retrieves a published ViewSet
Synopsis
integrity fetchviewset [--destination=value] [--[no|confirm]overwriteExisting [(-?|--usage)] [(-N|--no)] [(-Y|--yes)] [--[no]batch] [--cwd=directory] [--forceConfirm=[yes|no]] [--[no|Confirm=[yes|no]] [(-Ffile|--selectionFile=file)] [(-g|--gui)] [--quiet] [--settingsUI=[gui|default]] [--user=name] [--status=[none|gui|default]] [--hostname=server] [--password=password] [--port=number] viewset...
Description
integrity fetchviewset retrieves ViewSets that are available on the Integrity Lifecycle Manager Server and copies them to a specified directory. For details about the administration of ViewSets, see the Integrity Lifecycle Manager Help Center. For example:
integrity fetchviewset --destination=C:/ViewSets UserViewSet
|
|
The integrity fetchviewset command is useful for examining the contents of a ViewSet from a particular Integrity Lifecycle Manager Server and is not intended to be used for publishing the ViewSet to a different Integrity Lifecycle Manager Server. ViewSets contain references to other server objects by their IDs instead of their names. The consequence is that a ViewSet fetched from one server cannot be safely published to another server since the same ID may not represent the same object on both servers. For example, a ViewSet from server A may have a reference to an Integer field with the ID 71. If the ViewSet was published to server B where the field with ID 71 is a User field, the User field is referenced in the ViewSet instead of the Integer field.
|
Options
This command takes the universal options available to all
integrity commands, as well as some general options. See the
options reference page for descriptions.
• --destination=value
The destination directory for the ViewSet files.
• --[no|confirm]overwriteExisting
overwrites the existing ViewSet with the definitions from the retrieved ViewSet.
Diagnostics
See the
diagnostics reference page for possible exit status values.
See Also
