Problem with bar charts in 3.5

[FranziskaSumpf]

I am facing some problems with bar charts using the split by option. Instead of splitting the data by the chosen field, I just get duplicates.

This did not happen before! I got a new laptop with ArcGIS Pro 3.5.2. Not sure what the old one had, I think it was 3.4.x.

The error seems to be the same as in this post, where it occurred in 3.4 with scatter plots. However, that thread does not offer any solution.

I have narrowed it down a little bit, as the error only occurs when the layer has a join to another table. And it does not matter whether I chose fields from the original table or the joined table.

I have tried in a different project and with different data, the results are the same.

Has anyone else had this problem? How did you solve it? Or is it a bug? Has it been addressed? Any help is welcome! (I rely on bar charts a lot)

[ChristopherAllen · Accepted solution]

Hi @FranziskaSumpf ,

Thanks for reporting this! I can reproduce this bug going back to 3.5 and it appears that it's caused by the join so appreciate that you added that detail. This will be fixed in the upcoming 3.7 release, and we're aiming to also add the fix to the next 3.5 and 3.6 patch updates. In the meantime, if you're able to alter the input layer, you might consider using the Join Field tool to make the join permanent--the chart should work in that case. 

Take care,

Chris

[FranziskaSumpf]

Thank you, @ChristopherAllen, for the confirmation that this is a bug. Does it have a BUG Number I can watch out for? And I hope you can get the fix into one of the patches, because right now I am not sure when and if we will be able to move beyond 3.6 (due to the licensing changes).

[ChristopherAllen]

Hi @FranziskaSumpf , 

Here's the BUG link:

https://support.esri.com/en-us/bug/charts-with-the-split-by-option-do-not-display-correctl-bug-00018...

Once it's patched in 3.6, a note should be added to Version Fixed.

Take care,

Chris

[ChristopherAllen]

Hi @FranziskaSumpf , just a note that this will also be fixed in the upcoming 3.6.2 patch. Thanks!

[FranziskaSumpf]

@ChristopherAllen  Just got 3.6.2 and it is still a problem. Now the charts are empty as soon as I set a Split by field. ☹️

[ChristopherAllen]

Hi @FranziskaSumpf , I'm sorry to hear you're still having issues. The original reproduction case (where series values were duplicated across all series) appears to be fixed using our test data in 3.6.2. You said that you are now seeing the chart display as empty when you set a Split by, so answers to these questions would be very helpful:

* Are you ever seeing the original issue (duplicate values) at all now? Or is the chart always displaying as empty when you set the Split by field, so you never actually see any values?

* Are you using the same dataset and fields you were using in your original post?

* In your screenshot, it appears that the empty chart is a pie chart. Have you tried a bar chart?

Also, if you're able to share your dataset, please feel free to email me at callen@esri.com.

Thanks!

Chris 

[FranziskaSumpf]

Hi @ChristopherAllen , I've looked into it some more and can now say, that the problem only occurs in some cases. It just happened to affect all charts/layers that I tested on Tuesday.

But first, to answer your questions:

• No, as far as I can tell, the duplicate charts have not shown up again.
• Yes, same datasets, same layers, same project. The original error occurred with all my data, across all projects. Also if I recreate the affected charts with the original data in a different project the error occurs. 
• Bar charts and pie charts are both affected (have not checked other types)

But here's the catch:

I checked the chart from the original screenshot (with the four identical charts), and that one is okay now. As are other charts in that project with those data. However, the data that I work with daily shows the new error. I've tried to figure out where the differences are. So far I can tell, that it only seems to occur if there is more than one join involved, i.e. the feature class is joined to two separate tables (the order in which the tables where joined made no difference). If I delete all but one join I can create a chart with a split, as soon as I join a second table the chart breaks.

I have tried to recreate the error with some very simple feature classes and tables, but so far without success. I'll continue looking into it next week.

[ChristopherAllen]

Hi @FranziskaSumpf , thanks for the details. I was able to reproduce the chart breaking with multiple joins. I'll follow up soon. 

[ChristopherAllen]

Hi @FranziskaSumpf , I've actually been having trouble reproducing the multiple join issue since yesterday. If you are able to share your data (callen@esri.com), that would be very helpful.