Unable to UI componet Show payment Transaction Type and Payment Type on Braintree Settlement Report with PayPal through Braintree

[hirenrk4]

Preconditions and environment

Upon upgrading our production site from M2.4.3 to M2.4.6-p3 we discovered UI componet Grid unable to show Transaction Type and Payment Type. PayPal through Braintree

Steps to reproduce

1. Admin - Reports - Braintree Settlement Report
2. Filter with Transaction Type - Sale
3. Filter with Payment Type: paypal account
4. Apply Filter
5. Show result - https://www.awesomescreenshot.com/image/44791481?key=c7db77f5dddf781ff4feae86b300acce

Expected result

1. should be showing the result with the Transaction type
2. should be showing the result with the Payment type

Actual result

I can't seem to show the Transaction Type and Payment Type columns with proper results. when we export grid to CSV it is work fine. but the UI component Grid not working.works

Additional information

No response

Release note

No response

Triage and priority

• [X] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [X] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [x] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [x] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [X] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @hirenrk4. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

Hi @engcom-Dash. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
     - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[hirenrk4]

Hello @engcom-Dash

Glad to know you are working on this. please let me know if you need any help for my side. is there any update on this issue?

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Dash, here is your Magento Instance: https://cddb6075f2eb6f05f5f11e5a63b2a846.instances-prod.magento-community.engineering Admin access: https://cddb6075f2eb6f05f5f11e5a63b2a846.instances-prod.magento-community.engineering/admin_7253 Login: 8871d580 Password: e0755f990e29

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Dash, here is your Magento Instance: https://cddb6075f2eb6f05f5f11e5a63b2a846.instances-prod.magento-community.engineering Admin access: https://cddb6075f2eb6f05f5f11e5a63b2a846.instances-prod.magento-community.engineering/admin_3bf4 Login: 0f5be097 Password: fdb64b29579e

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Dash, here is your Magento Instance: https://cddb6075f2eb6f05f5f11e5a63b2a846.instances-prod.magento-community.engineering Admin access: https://cddb6075f2eb6f05f5f11e5a63b2a846.instances-prod.magento-community.engineering/admin_2947 Login: cf366cf1 Password: 17842354ca16

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-10853 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Dash. Thank you for verifying the issue.
Issue Available: @engcom-Dash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[engcom-Hotel]

Hello @engcom-Dash,

As per the discussion in the triage call please verify this issue in the latest released version as well as the latest development branch.

Moving this issue back to "Ready for confirmation".

Thanks

[engcom-Dash]

Hi @hirenrk4

Thank you for reporting and collaboration.

Verified the issue on 2.4.6-p3 after upgrading from 2.4.3 and in 2.4.7-beta2 . The issue is reproducable.

We are not able to see the transaction type and payment type on braintree settlement report with payapal through braintree.

Please refer the attached screenshots.

[github-jira-sync-bot]

:x: Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-10853