Resource event deltas
When two-way sync is on, Dime.Scheduler does not reread a resourceResourceAn entity that can carry out work - a person, vehicle, tool, or room - that you schedule on the planning board.'s whole calendar every time. It asks Exchange for what changed since the last pass, over the window set on the Exchange setup, and keeps the answer: a resource event deltaResource event deltaThe change set the Exchange connector received from a resource’s mailbox for one sync window. The Deltas page lists them so you can see what Exchange actually sent.. The Deltas page lists those change sets per resource, so when an Outlook change did not arrive on the planning boardPlanning boardThe main graphical scheduling surface where dispatchers drag tasks onto resources across a timeline. as expected you can see what the connectorConnectorAn integration that links Dime.Scheduler to a back-office system, routing data in and scheduling decisions back out. actually received for that person and in which window, instead of guessing.
Open it from the Exchange section of the navigation, or visit https://app.dimescheduler.com/resourceeventdeltas.
Layout
The page is split into two panes:
- Left - the resources that have the Exchange integration enabled, listed by display name. Pick one to load its deltas; click it again, or Clear, to deselect. The magnifier opens a search box that narrows the list as you type (Escape closes it).
- Right - the delta grid for the selected resource. Until a resource is picked it only says Select a resource to view its event deltas.
The splitter between the two panes can be dragged to widen either side.
Reading the grid
| Column | Description |
|---|---|
| Start | Start of the window the change set covers. |
| End | End of that window. |
| Delta | The change set as received, rendered in monospace so that timestamps and identifiers line up. Hover a cell to read it in full. |
Newest windows come first. All three columns can be sorted by clicking their header, and filtered from the column menu: dates on Start and End, text on Delta. Rows can also be grouped by a column.
Below the grid, the pager steps through the list a page at a time. The page size can be set to 25, 50, 100 or 200 rows, and the reload button fetches the current page again, which is the quick way to check whether a sync that just ran left a new delta.
Export downloads what is currently loaded as an Excel file (resource-event-deltas.xlsx), useful when you want to hand a sequence of deltas to support.
Deleting deltas
Each row has a trash icon on the right that removes that one delta. To clear several at once, select the rows and use the Delete (n) button that appears above the grid, where n is the number of selected rows; pressing the Delete key with rows selected does the same. Either way a dialog asks Are you sure you want to delete the selected resource event delta(s)? before anything is removed.
Deleting a delta only clears Dime.Scheduler's record of what it received. It does not touch the Exchange calendar and it does not undo whatever the sync already did with the change.
Related
- Two-way sync - how Dime.Scheduler and Exchange exchange calendar data.
- Exchange logs - the raw connector log stream.
- Transaction Errors - diagnosed appointment failures with
DSEXcodes.