This repository has been archived by the owner on Jun 2, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
ea516dc
commit d779d48
Showing
1 changed file
with
8 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,10 @@ | ||
# PowerShell_Import_Export | ||
This repository contains two PowerShell scripts for an easier way of handling import/export of jobs from a folder level in JAMS version 6.x | ||
|
||
Included are two powershell scripts. By default our Export-JAMSXml cmdlet will only export one job or folder at a time. | ||
|
||
The Export PowerShell script was built to be able to export all jobs within a given folder in a two step process. First it exports all of the job names and then the full job definitions. | ||
|
||
The Import PowerShell script allows the user to import the xml file with just the job names so the job definitions are created first to avoid any dependency issues and then the user would import the full job definitions from the second export file. | ||
|
||
If a user tries to import jobs that have dependencies attached to them and those dependencies are not imported first, the import will fail. This ensures that a "shell" of all of the jobs are imported first that way dependencies are covered. |