We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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:
Expected behavior The Customer Journey Scheduling visual should be populated with a Gantt style visualizer showing customer journeys.
Screenshots
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-
The text was updated successfully, but these errors were encountered:
This was resolved by changing "Journey Status" in the legend area to "Journey Name". These fields must match according to the MAQ software issue.
Sorry, something went wrong.
No branches or pull requests
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:
Expected behavior
The Customer Journey Scheduling visual should be populated with a Gantt style visualizer showing customer journeys.
Screenshots
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-
The text was updated successfully, but these errors were encountered: