S-142-V1-EN
In this article, we go over the issues you may encounter while importing data from one schedule to another and offer troubleshooting steps.
Locked duty/vehicle
Note: When importing data, you can choose to only apply changes to the unlocked rows in the target schedule by checking the corresponding box. The issue described below is only relevant to cases when this box is checked.
Projection will not apply changes to a duty if it’s associated with a locked vehicle in your schedule. This rule also works the other way around - if a duty is locked, projection will not work on the vehicle associated with it.
Make sure the relevant trips and vehicles are unlocked in your target schedule.
Unassigned attendance events
Upon projection, you may find unassigned attendance events in your stack. This is often caused by revising attendance while there are relief cars and/or public transport travels in your schedule. The system tends to avoid changing those, leaving the attendance events unassigned as a result.
To solve this, try revising attendance, duty travel, and signing events together:
Route already exists in the schedule
You may encounter an error that says the following:
“A route that was added from the origin schedule already exists in the target, but with different properties”.
In this case, please reach out to the Optibus Support team for assistance.
Trips left in the stack
Some trips may be left in the stack upon projection. A possible reason is that the Vehicle Type for those trips was changed in the timeplan and not updated. In this case, run another projection and check the Ignore vehicle types box:
This will allow the trips to be assigned back in the Gantt view.
