Connector Improvement: BrightFlag connector is not loading the correct status of rejected invoices
Answeredthe invoice 1070030414 was first loaded in the brightflag as approved invoice and was loaded in our snowflake as an approved invoice, later this invoice was rejected in brightflag and another invoice was laoded (id: 3772531). This invoice was later marked as paid. Now for invoice id 3772531 we can see the correct status in the database but for id 3661174 the status is still approved which is rejected in brightflag.
I did check using API, api link: https://app.brightflag.com/api/v1/invoice-summary and when I got the invoices from the API I got the invoice details for id 3772531, but the details for id 3661174 are not there. It seems the API does not bring in the rejected invoices. In FiveTran for these invoices can we get the _FIVETRAN_DELETED status to true, so it is easy to identify the invoices that are rejected or deleted from brightflag, as the status field is not providing correct information.
-
Official comment
Hi Siddhant,
This appears to be a bug with how the BrightFlag connector handles rejected invoices. Specifically, when an invoice is rejected in BrightFlag and no longer appears in the API response, the connector should mark the corresponding record in your destination with
_FIVETRAN_DELETED = true. Currently, this is not happening for invoice id 3661174, leading to an incorrect status being reflected in your Snowflake database.We'll investigate this issue further to ensure that rejected or deleted invoices are accurately flagged in your destination tables. Updates will be provided here as we progress.
Thanks,
Syead
Please sign in to leave a comment.
Comments
1 comment