microsoft / Dynamics-365-for-Marketing---Power-BI-Reporting

Download these Power BI templates to start building custom analytics and reports based on your Dynamics 365 for Marketing data. These templates will help you to connect to your Dynamics 365 instance and access its data. The download includes the following templates: Power BI template for Dynamics 365 for Marketing: Includes the code required to connect to your Dynamics 365 for Marketing data, and also includes functions that you can call to load entity and interaction data with just one line of code. This template provides a basic starting point for building your own custom reports. Sample email marketing analytics report: Provides a comprehensive report of your email marketing results, including detailed analytics, charts, and views spread across multiple report pages. You can use this template as-is, or as inspiration for designing your own reports.
MIT License
47 stars 19 forks source link

Gantt chart visualizer on Email Marketing Analyzer error. #9

Open odetonoise opened 3 years ago

odetonoise commented 3 years ago

Describe the bug Customer Journey Scheduling Gantt visualizer generates "Please select a field that is already present in category"

To Reproduce Steps to reproduce the behavior:

  1. Load Email Marketing pbit file.
  2. Generate connections in line with documentation
  3. Click on marketing plan tab.
  4. See error "Please select a field that is already present in category"

Expected behavior The Customer Journey Scheduling visual should be populated with a Gantt style visualizer showing customer journeys.

Screenshots PowerBIError

Data Connection Not relevant to the issue.

Additional context Add any other context about the problem here.

Error message is described in the MAQ Software community (supplier of Gantt chart visualization) below.

https://maqsoftware.zendesk.com/hc/en-us/community/posts/360077235352--Gantt-Chart-Error-message-Please-select-a-field-that-is-already-present-in-category-

odetonoise commented 3 years ago

This was resolved by changing "Journey Status" in the legend area to "Journey Name". These fields must match according to the MAQ software issue.