Add the moment the UTC Handling BC consistent, e.g., if you call the Function => CalcRoutingLine.CalculateRoutingLine(Rec, Direction::Forward, false); from a Button or from a Web service on the same data it will produce different data (as long you are not living in UTC Time). It is also testable if you move your PC to another Timezone and run the CalculateRoutingLine funktion. Produces the same Problem, everything is recalculated with the Session of the User that is in a different Timezone then the rest of the BC data.

The Problem is that he CalculateRoutingLine is converting DateTimes with Offset to a Date and a Time with no Offset.

To solve this kind of Problems, we have the following Ideas:

1. Allow the Web service to run in the same Timezone then BC is running in. We see this as the best option for now, because Idea No. 2 takes too long to make it in all areas
2. You fix the all places where you convert date time with Offset to Date and Time
3. Allow to start a JobQueueEntry by a function call. This would allow the Developer to execute the Code directly but in the Timezone of BC

As long, you do not come up with a Solution, no one can use the Function CalculateRoutingLine via Webservice. We from our side will split now the code that we first save every thing in Database and a Job that runs every 60 sec will check if there was a change in Data and will then execute CalculateRoutingLine => my developer soul burns in pain.