{"section":"known-issues","requestedLocale":"en","requestedSlug":"order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api","locale":"en","slug":"order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api","path":"docs/en/known-issues/Payments/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md","branch":"main","content":"## Summary\n\n\nConnectors from that list need to save more fields for the connector that works with “Venda direta” - Sales app. Specifically, for the connectors listed below, and only for them, all content from the payload should be directed to the \"`connectorResponses`\" field. This results in a duplication of the \"`tid`\" field, which already exists in the \"`connectorResponses`.\" While this duplication does not pose a problem in terms of the transaction life cycle, it does create an inconsistency when generating reports from the order page.\n\n\n- PagarMeV3\n- PagarMeV3Stg\n- Adyen V3\n\n\n##\n\n## Simulation\n\n\n\n1. Access the admin order page.\n2. Generate the order report.\n3. Look for the `tId` column where the orders were placed using one of these connectors\n\n\n##\n\n## Workaround\n\n\nUse the /payment route or the GET order API to retrieve this data"}