Schedule Import
Schedule Import release notes pertain to importing and modifying schedule information.
| Version | Type | Description | ID |
|---|---|---|---|
| 19.0.5.0 | CORR | The issue of Schedule Import checking for activated days using an FX SignID causing the import to fail has been fixed. | OPS-20492 |
| 19.0.5.0 | CORR | The issue of runs with the same SourceRunIds and Run Names having different RunIds when a re-import was performed has been fixed. The issue occurred after re-importing when there were new runs and runs with more than one exception combination. | OPS-20749 |
| 19.0.6.0 | CORR | The sign-up period is now shown in the BlockBuster Sign-up for Import field after it is selected for the first time in the Context dialog box of the Schedule Import screen. | OPS-21178 |
| 19.0.8.0 | CORR | There was an issue in Schedule Import where rosters could not be imported because the initial FX Runs Schedule Import did not populate the OriginDivisionId field. Now, division information is populated when rosters are imported for the first time. | OPS-22271 |
| 19.0.8.0 | ENH | There was an issue in the Shorten Sign-Up Period dialog box where the Affects Holiday section did not appear to be populated. Now, four sections are available: Affects Bids, Division Bids, Holidays in Bids, and Affects Holidays. | OPS-17041 |
| 19.0.8.0 | ENH | Validation messages that appear during mid-sign up imports are now more descriptive about what has been changed to cause an error. For example, a LineName change or a DirectionName change. | OPS-21142 |
| 19.0.10.1 | CORR | An issue where extending a sign-up period resulted in a primary key violation has been fixed. | OPS-22523 |
| 19.0.10.1 | CORR | There was an issue where overlapping LineGroupAbbr values resulted in driver blocks being imported without all of the required information (some from times, to times, drive block details, line details, and trip details were missing). Now, if UseDriverBlocks information is changed in FX, a message appears asking that the data be fixed. If only the LineGroupName is changed, a warning message appears and the system updates LineGroupNames as needed. | OPS-22475 |
| 19.0.13.0 | CORR | Critical: An occasional issue where an assert error would occur when performing a Schedule Import or Mid-signup import has been fixed. | OPS-23667 |
| 19.0.16.0 | CORR | An issue where importing more than two FX holidays when the first FX holiday was not already in OPS Holiday and the second Holiday ID was the Max Holiday ID + 1 resulted in an SQL error has been fixed. | OPS-24633 |
19.0.20.0 |
ENH | Critical: An issue in mid-signup imports where roster changes were not imported as expected when Runs in Signup without runversionid=0 records were included has been fixed. | OPS-25548 |
19.0.20.0 |
CORR | An issue in Sign-Up Period Management where extending a sign-up period didn't extend records for some volunteer types was fixed. | OPS-25768 |
19.0.21.0 |
CORR | An issue when importing from Trapeze FX using Schedule Import where a second record was created when line names appeared in a different case (lowercase vs. uppercase) has been fixed. Now, if the only line abbreviation difference between the existing record and the new record is its case, OPS updates the current line with the newly imported line information. | OPS-25897 |
19.0.22.0 |
CORR | Fixed an issue where using the Import Into An Existing Sign-Up Period functionality in OPS Sign-Up Management resulted in overlapping and invalid data. | OPS-26680 |
19.0.23.0 |
CORR | Critical: Fixed an issue where the ability to delete a sign-up period by right-clicking and selecting Delete could be enabled even when the Delete Sign-up Period option in the menu bar was disabled. Both methods of deleting a sign-up period are now uniformly enabled or disabled. | OPS-17669 |
19.0.26.0 |
CORR | Blocker: An issue in Schedule Import where an assert error occurred when using SQL 2016 and below was fixed. | OPS-29826 |