Kantata OX: add role_id to TIME_ENTRY table
AnsweredConnector name: Kantata OX
Table name: TIME_ENTRY
Column to add: role_id
API documentation link: https://developer.kantata.com/kantata/specification/time-entries/get%20time%20entries
Context: The role_id field is returned by the Kantata API on the
time_entries endpoint but is not currently synced into the
TIME_ENTRY table. Without it we cannot attribute logged hours to
the role a person was billing under, which is required for our
invoicing workflow.
We would also request a historical backfill once the column is
added, so existing time entries carry the value.
Additional details:


-
Official comment
Hi Leonardo,
Thank you for submitting this request. This is a valuable idea, and I have added it to our backlog for feature improvements for the Kantata OX connector. Your request to include the
role_idin the TIME_ENTRY table, as well as the need for a historical backfill, is clear from your context regarding invoicing workflows.We will keep this thread updated with any progress or changes regarding this feature.
Thanks,
Frank -
We have the same issue, and as I had to work around it by querying the Kantata API directly and joining the data up with Fivetran's extract: this feature seem to require a minimal change to the way Fivetran pulls data, and that's to add role to the include query parameter. Seems like many of the other options (like story, and workspace) are automatically enabled/used by Kantata, but role is not one of them.
Given how there's nothing user-adjustable in Fivetran's export, probably adding all the includes would make sense, though definitely the role is the key missing one I've seen so far.
I would file this this as a bug, rather than a feature request, given that for any reasonable use of time entries, this is a necessary information, that was probably overlooked so far.
Thanks!
Please sign in to leave a comment.
Comments
2 comments