- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Visual Legend - Repeated indices found in GroupBy or Projections
Today after preparing the base model (dimensional) for the data, i set out to explore it a bit.
All worked fine, until suddently whilst adding legends to my graphs, I always get this error when using information from the fact table: "Couldn't load the data for this visual. Repeated indices found in GroupBy or Projections".
The error isn't exactly explicit, but I assume this might be related with the fact that I'm appending multiple CVS together; from which I then build the facts and dimensions directly on PBI, and the indices are somehow messed up.
Has anyone had this problem before?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Dear v-lionel-msft,
I apologize for the late reply. Oddly the enough, the problem seems to have fixed itself. What seems to have triggered the correction was the use of DAX Studio to export the tables one by one. I'm assuming this was a memory key allocation conflict by PowerBI from using multiple append queries, but I can only assume.
Once again, thank you for your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Ran into the same error here and fixed it by removing the conditional color before applying the legend. I think the reason for this case is that, some conditional colors have already been applied, and adding a legend column will triggers another usage on multiple colors. Then there's conflict on the color applying rules, and Powerbi just couldn't determine which rule to use for the colors. To solve such confict, you could just give up on either the legend or the conditionale color.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Ran into the same error here and fixed it by removing the conditional color before applying the legend. I think the reason for this case is that, some conditional colors have already been applied, and adding a legend column will triggers another usage on multiple colors. Then there's conflict on the color applying rules, and Powerbi just couldn't determine which rule to use for the colors. To solve such confict, you could just give up on either the legend or the conditionale color.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

100% @DanT this is the solution.
If I took the time to answer your question and I came up with a solution, please mark my post as a solution and /or give kudos freely for the effort 🙂 Thank you!
Proud to be a Super User!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

I had the same issue. Thank you DanT, your solution solved the problem 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Hi,
Have a similar issue when for the given table:
Date | Category | Col 1 | Col 2 |
1/1/2020 | 1 | 123 | 21 |
1/1/2020 | 2 | 143 | 32 |
1/1/2020 | 3 | 123 | 12 |
1/2/2020 | 1 | 234 | 32 |
1/2/2020 | 2 | 432 | 43 |
where I calculated the measure X=Divide (sum(Col 1), sum(Col 2)).
When I drag the column Category to the 'legend' box of a line chart (with date as 'axis' and X as 'values') I get the error message "Repeated indices found in GroupBy or Projections"
Thanks for your help
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Hi @GuilhermeB ,
The problem is that there is a grouping and aggregation conflict between the fields of X axis and the Legend.
Please show me the sample data model, I will check it for you.
Best regards,
Lionel Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Dear v-lionel-msft,
I apologize for the late reply. Oddly the enough, the problem seems to have fixed itself. What seems to have triggered the correction was the use of DAX Studio to export the tables one by one. I'm assuming this was a memory key allocation conflict by PowerBI from using multiple append queries, but I can only assume.
Once again, thank you for your help.

Helpful resources
Join us at the Microsoft Fabric Community Conference
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Power BI Monthly Update - February 2025
Check out the February 2025 Power BI update to learn about new features.

Subject | Author | Posted | |
---|---|---|---|
10-15-2024 09:00 AM | |||
05-14-2024 01:35 PM | |||
09-10-2024 04:28 AM | |||
07-07-2024 09:01 AM | |||
10-11-2024 12:59 AM |
User | Count |
---|---|
88 | |
73 | |
54 | |
43 | |
37 |
User | Count |
---|---|
98 | |
65 | |
54 | |
48 | |
45 |