Auto Set Baseline Dates

 

The Set Baseline Dates command can be executed from a command/batch file.  The auto execution command is:

"AutoSetBaseLineDates=C:\Dynafact\SetBaseLineCommandFile.txt" 

 

Where SetBaseLineCommandFile.txt has the options for setting the baseline dates.  The command must be surrounded in double quotation marks.  A complete command line would include the typical auto execution commands as in the example below:

"C:\Program Files (x86)\Dynafact\ DMSEnt.exe" "UserIniFolder=C:\Dynafact\Production\DMS\User\" "AutoUserName=DMS" "DatabaseName=DMS113" "AutoSetBaseLineDates=C:\Dynafact\SetBaseLineCommandFile.txt" AutoLogOut

 

The command file parameters are:

1.OrderNumber=
The Order Number(s) to set baseline dates.  The SQL wild cards % and _ (underscore) can be used in the Order Number.  The Order Number parameter can be left out if the Set Baseline Dates is going to be performed by Job States.  Both the Order Number and the Job States can be given.

2.JobState=Job State 1; Job State 2; Job State 3…
A list of Job States can be given for the jobs that need to have their baseline dates set.  Each Job State is separated by a semi colon and the Job States must exist in DMS.

3.SetJobBaslineDates=
To set the Job Baseline Dates, use the command SetJobBaslineDates=Yes.  The default is No.

4.OnlySetJobBaslineDatesIfBlank=
To only set the Job Baseline Dates if the current dates are blank, use the command OnlySetJobBaslineDatesIfBlank =Yes.  The default is No.

5.SetOperationBaslineDates=
To set the Operation Baseline Dates, use the command SetOperationBaslineDates=Yes.  The default is No.

6.OnlySetOperationBaslineDatesIfBlank=
To only set the Operation Baseline Dates if the current dates are blank, use the command OnlySetOperationBaslineDatesIfBlank =Yes.  The default is No.

 

If setting Operation Baseline Dates, one of the following commands can optionally be used to set the Schedule Dates if an operation’s Schedule Dates are blank.  The setting of Operation Schedule Dates takes place before setting the Operation Baseline Dates.  Only one of the four commands should be used.  Parameters are not required for commands 1 through 3; the command SetBlankScheduleDatesToNewDate= requires a date after the = sign in the Windows date format.

 

1.LeaveScheduleDatesBlank
This command is the default and will leave the Operation Schedule Dates blank.

2.SetBlankScheduleDatesToJobReleaseDate
This command sets any blank Operations Schedule Dates to the Job’s Release Date.

3.SetBlankScheduleDatesToJobScheduleStartDate
This command sets any blank Operations Schedule Dates to the Job’s Schedule Start Date.

4.SetBlankScheduleDatesToNewDate= <date in Windows Date format>
This command sets any blank Operations Schedule Dates to the given date.  The date given must be in the current Windows date format.  For example, if the Windows date format is mm/dd/yy and September 15, 2023 is the date to set all blank Operation Schedule Dates to, the command would be SetBlankScheduleDatesToNewDate=09/15/23

 

The example below shows a Set Baseline Command File that will:

1.Select all Order Numbers that start with MO and are followed by any characters.

2.Select Job States Forecast, Rework and Schedule only.

3.Set Job Baseline Dates

4.Only set the Job Baseline Dates if they are blank.

5.Set Operation Baseline Dates

6.Set the operation baseline dates regardless of their current values.

 

OrderNumber=MO%

JobState=Forecast;Rework;Schedule

SetJobBaslineDates=Yes

OnlySetJobBaslineDatesIfBlank=Yes

SetOperationBaslineDates=Yes

OnlySetOperationBaslineDatesIfBlank=No

 

Since a command to set blank Operation Schedule Dates was not given, the default LeaveScheduleDatesBlank is used.