Connector Improvement: Capture updates for “Scope” field in Wrike Task table
AnsweredWrike’s API shows a named field called “scope” and is part of the Task table response.
It’s a string field and the values are:
- WsRoot - Virtual root folder of account
- RbRoot - Virtual Recycle Bin folder of account
- WsFolder - Folder in account
- RbFolder - Folder is in Recycle Bin (deleted folder)
- WsTask - Task in account
- RbTask - Task is in Recycle Bin (deleted task)
This is critical to the Task data because it is valuable to know if a task was moved to the Recycle Bin or not. In some of our reporting we are getting tasks that have actually been moved to the Recycle Bin when comparing to the Wrike interface, but we have no way to filter them out because this field is not present.
We have the field in the FiveTran table but it does not update when this field is updated in the Wrike API. We would expect this field to be updated in FiveTran upon any updates to the “scope” field value.
We were shown the below example API call from FiveTran and would like to see the “scope” field included as a field in this list if it’s updated in the Wrike data:
--header 'User-Agent: Jersey/2.39' \
--header 'Authorization: Bearer <redacted>' \
--header 'Accept: application/json'
-
Official comment
Hi Weston,
Thank you for your feature request regarding the "scope" field updates in the Wrike Task table. Currently, our strategic focus is on enhancing core value areas, and this specific update is not part of our immediate plans. However, we will track your interest and consider it in future evaluations. We appreciate your feedback and encourage you to continue sharing insights that help us align with users' needs.
Best,
Sanjeevv Maniram
Please sign in to leave a comment.
Comments
1 comment