Error in Advanced Reporting Business Intelligence Tools

[lolareifs]

Preconditions and environment

• Magento version 2.4.3

Steps to reproduce

• Go to Reports > Business Intelligence > Advanced Reporting Note:
• The website must run on a public web server.
• The domain must have a valid security (SSL) certificate.
• Commerce must have been installed or upgraded successfully without error.
• In the Commerce configuration for store URLs, the Base URL (Secure) setting for the store view must point to the secure URL. For example: https://yourdomain.com/.
• In the Commerce configuration for store URLs, Use Secure URLs on Storefront and Use Secure URLs in Admin must be set to Yes.
• Make sure that Commerce crontab is created and cron jobs are running on the installed server.
• Advanced Reporting can be used only with Commerce installations that have continually used a single base currency.
• We need to enable Advanced Reporting: Stores > Settings > Configuration. General -> Enable Advanced Reporting Service .
• Set the time and select Industry. Save. Clear cache. After the cron run successfully for selected time, Reports can be accessed from the dashboard.
• Wait overnight, or until after the time of your next scheduled update. Then, check the status of your subscription. If the status is still pending, make sure that your installation meets all requirements.

Expected result

You should get access to five dashboards with approximately 70 reports

Actual result

GO to https://experienceleague.adobe.com/docs/commerce-admin/start/reporting/business-intelligence.html#advanced-reporting

Additional information

When the cron "analytucs_subscribe" is executed (which activating the conection with the BI service) I get the next error:

[2022-10-26 14:15:48] main.WARNING: Subscription for MBI service has been failed. An error occurred during token exchange: {"message":"We are unable to connect to your store. Your certificate is invalid."}. Content-Type: application/json;charset=UTF-8 [] []

The integration token is rigth and has the rigth permissions. Magento API has accesibility (tested in Postman)

No response

Release note

No response

Triage and priority

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

[m2-assistant[bot]]

Hi @lolareifs. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

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.

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant[bot]]

Hi @engcom-November. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components 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!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Hi @lolareifs , Thank you for reporting and collaboration. As per Magento devdocs, Magento instance should comply with below requirements in order to enable / work with Advanced Reporting.

Requirements:

1. The website must run on a public web server.
2. The domain must have a valid security (SSL) certificate.
3. Commerce must have been installed or upgraded successfully without error.
4. In the Commerce configuration for store URLs, the Base URL (Secure) setting for the store view must point to the secure URL. For example: https://yourdomain.com.
5. In the Commerce configuration for store URLs, Use Secure URLs on Storefront and Use Secure URLs in Admin must be set to Yes.
6. Make sure that Commerce crontab is created and cron jobs are running on the installed server.
7. Advanced Reporting can be used only with Commerce installations that have continually used a single base currency.
8. We need to enable Advanced Reporting: Stores > Settings > Configuration. General -> Enable Advanced Reporting Service . Set the time and select Industry. Save. Clear cache. After the cron run successfully for selected time, Reports can be accessed from the dashboad.
9. Wait overnight, or until after the time of your next scheduled update. Then, check the status of your subscription. If the status is still pending, make sure that your installation meets all requirements.

Kindly recheck the behavior on Magento 2.4-develop instance with above conditions checked and let us know if you are still facing any issues. Thank you.

[lolareifs]

Hello, We have reviewed all the conditions that indicate us but unfortunately everything was correct and the reports continue to not work. Thanks in advance, Greetings

[soledc]

Hello, I'm having the same problem with BI reports. The settings are as indicated. Is there any other option? Version: Magento 2.4.3 Thank!

[engcom-November]

Hi @lolareifs , As the issue cannot be reproduced on local Magento 2.4-develop instance which have unsecured URL, test environment setup in progress to check on public web server. Thank you.

[soledc]

Hello, Is there any news about the testing of the issue? Thank you.

[engcom-November]

Verified the issue on Magento 2.4.5 instance public web server and the issue is reproducible. Unable to access reports from Advanced Reporting even after following all the steps mentioned in comment Hence confirming the issue.

[github-jira-sync-bot]

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

[m2-assistant[bot]]

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

[github-jira-sync-bot]

:x: You don't have permission to export this issue.