Enhancement Request: Add "Reasons" Field to Coupa Connection "Approval" Table
Currently, the "Reasons" field available in the Coupa "Approval" table is not being replicated through Fivetran and does not appear to be included in the existing ERD/schema.
This field is required for reporting and analysis purposes. We request that the "Reasons" field be added to the Coupa's Approval table and included in the Fivetran replication process to ensure it is available for downstream reporting and analytics.
-
Hi Namrata,
I am the PM for Coupa and I am currently taking a look at the above request. I'll update this ticket shortly with more information.
-
Hi Rohan,
Thank you for checking. Since this requirement is urgent, could you please prioritize it?
-
Hi Namrata,
Thanks for sharing the priority. I am working on analysing this request and estimating the effort. I'll reach out to you if any further information is needed.
-
Hi Namrata,
I am sharing the details of the analysis done and my recommendation for the path forward. Can you please review these details and share your feedback, if any?
API analysis
-
The
/approvalendpoint contains thereasonsfield as identified by the customer, as per these source API docs. -
The
reasonsfield is a list of strings. Screenshot of an API call has been attached below.

-
The model class for the
APPROVALtable already contains theList<String> reasonsfield. Screenshot of the same has been attached below.

-
It is not known why this field is annotated with
@CsvIgnoreand whether any decisions were made to ignore this field from being synced.
Sync strategy
The sync strategy for syncing the
reasonsfield is as follows: All the values can be congregated into a string and synced as 1 single field namedreasons. -
-
Hi Namrata,
This enhancement request is completed and the "Reasons" field has been added to the "Approval" table. Please review this enhancement and feel free to share any feedback that you may have.
Please sign in to leave a comment.
Comments
5 comments