Coupa Connector Request
Which connector?:
coupa for Databricks Dev & Prd
Additional details:
Per support ticket # 417441, we were informed that when a quote_supplier record is present in both the quote_request and quote_response endpoints, the quote_response_id is populated in the quote_supplier table while the quote_request_id is set to NULL. As a result, the relationship to the original quote_request record is not retained, which can lead to incomplete results when joining quote_request to quote_supplier for reporting and analytics purposes.
We would like to request an enhancement to preserve both quote_request_id and quote_response_id when a quote_supplier record exists in both endpoints. Retaining both relationships would provide a more complete representation of the quote lifecycle, improve traceability, and support more intuitive joins and reporting use cases without requiring additional workarounds.
-
Official comment
Hi Atreyee,
This request is complete and is live.
In order to ensure historical records are backfilled with appropriate value in the
quote_request_idcolumn, please ask customer to perform a resync of theQUOTE_SUPPLIERtable by performing a reysnc of the parentQUOTE_RESPONSEtable.Thanks,
Rohan -
Hi Atreyee,
"Coupa Connector Request" is in progress wherein the development is complete and the deployment is in progress. I'll update this ticket once the fix is live and available for you to start using.
I'll post further updates here as we progress.
Thanks,
Rohan
Please sign in to leave a comment.
Comments
2 comments