When you use the DSE for scheduling, could you explain the best way to export the data available when you are in “tentative status”.
For a technician journey, we would like to summarize : time travel, distance travel, time on Service order, etc. These data are available in the Activity Details by service order The idea is to summarize data for the whole day for a technician.
Thanks and Regards anthony
Best answer by Phil Seifert
Hi Anthony,
Confirmation from R&D is that we don't have any queries or tools on hand to do what you are asking. It was suggested that you search Google for tools that convert & parse the format.
The JSON format was used to minimize the size of the data on the database and size of the transport data between client & server.
No one is aware of any customers who might be doing something like this already.
Hope you can find something that will help you somewhere but this is not something we have available.
The calls which are in Tentative status are not committed to the database in the demand or demand labor tables thus are not available for exporting in a usable form for reporting. R&D confirms this when I inquired with the DSE experts:
DSE only saves the schedule data on ‘dse_schedule’ &’ demand_schedule’ tables.
For tentative calls the data doesn’t save on demand table.
The dse_schedule table only contains raw_plan and committed_plan columns where all the data for the plan is embedded internally, not as separate columns for queries.
Confirmation from R&D is that we don't have any queries or tools on hand to do what you are asking. It was suggested that you search Google for tools that convert & parse the format.
The JSON format was used to minimize the size of the data on the database and size of the transport data between client & server.
No one is aware of any customers who might be doing something like this already.
Hope you can find something that will help you somewhere but this is not something we have available.
Demand_Schedule’ table is always with the most updated DSE schedule for each session. For each schedule DSE overrides the data for the session with the last updated schedule session.
DSE_schedule’ table save all the DSE schedule data, there is a process that delete the old data after few days. The deletion process is to avoid huge data on DB.
For the link, when I look at the DB schema, I see:
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.