+ Start a Discussion
S_2013S_2013 

Dashboard deplyment error?

I am trying to deploy 3 reports and 6 dashboard components (2 on each underlying report) when I get this starnge error:

The values of chartSummary and/or groupingColumn are not compatible with the autoselectColumnsFromReport mode for ColumnStacked

 

But the issue is that, the autoselectColumnsFromReport is false(as it should be) and my stacked bar chart in the dashboards have the correct groupings and summerizing and are in sync with the underlying reports(they work fine in source system)

The target system has NO reports and dashboards so no question of any conflict.

Did anyone face similar issue?

 

Thanks in advance

Sankalita

Ashish_SFDCAshish_SFDC

Hi Sankalita, 

 

Please try and let us know if the below steps solve this issue. 

 

1. You will need to extract the dashboard metadata from the packaging org. 
2. Locate the problematic dashboard and it will be in a folder of the same name 

View the source of this which should look something like this: 

<components> 
<autoselectColumnsFromReport>false</autoselectColumnsFromReport> 
<chartSummary> 
<column>FORMULA3</column> 
</chartSummary> 
<componentType>Metric</componentType> 
<displayUnits>Integer</displayUnits> 
<header>Utilization</header> 
<indicatorHighColor>#54C254</indicatorHighColor> 
<indicatorLowColor>#C25454</indicatorLowColor> 
<indicatorMiddleColor>#C2C254</indicatorMiddleColor> 
<metricLabel>My YTD Utilization, in %</metricLabel> 
<report>PSA_Reports/Util_My_Util_YTD_by_Month</report> 
</components> 

and add <axisBinding>y</axisBinding> to the chart summary section like this 

<chartSummary> 
<column>FORMULA3</column> 
<axisBinding>y</axisBinding> 
</chartSummary> 
 
Regards,
Ashish
If your question is answered, Please accept this post as Solved. 
 
 
S_2013S_2013
Hi Ashish,

Thank you for your message.. But the issue was somewhere else. It is
actually related to the api name of the underlying report to the dashboard.
One of the dashboard component's source report had its api name changed and
this was giving the error. The confusing part is that, even if you change
the api name, in the same environment you will not find any issue, but
during deployment you will get the issue... so we had to recreate the
dashboard component in source env and thereafter migrate...

Thanks again for helping out!
Sankalita