Connector Improvement: Dialpad: call_center_operator_duty_status should not be a snapshot table
Answered
Which connector?: Dialpad
Additional details:
The table call_center_operator_duty_status is currently functioning as a "snapshot" table. Within dialpad itself, this data is stored historically, allowing users to view an operators status changes over time. Ie: This operator was on duty from 8am - 5pm on 6/5. The PK on the table is only the operator ID, so the status is overwritten on every run leaving the table as a view of the current status.
Without the historical rows, this table is useless for our reporting purposes.
-
Official comment
Hi Steven,
Thank you for flagging this limitation with the call_center_operator_duty_status table. We have added this to our active backlog and are reviewing what it would take to preserve historical duty status rows rather than overwriting on each sync.
We will keep you updated on this thread as we make progress.
Please sign in to leave a comment.
Comments
1 comment