The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
Hi...
I have a clustered bar chart, where both the x-axis and y-axis display information from field parameters which choose the selected fields from the fact table. When data is exported from the chart, 2 non-appealing issues happen:
Exported data column headers appear like this
This is how the clustered bar chart is setup. "Category Label" is a parameter, and "Info Label" is a parameter
Category Label parameter definition: It is a 2 level parameter, user chooses either Item Category (Grp Label = 0) or business category (Grp Label = 1) controlled by the last column in the parameter table, then the corresponding parameter values (Catg-1 ...4 or Business Catg) are displayed
Info Label parameter definition is again a 2 level field parameter. User chooses either Amounts (Group ID = 0) or PO Count (Group ID = 1) then the corresponding data is displayed (Ordered/Delivered amounts or PO Count)
Is there a way to control the column headers in the exported data table and to prevent the dynamic format string from being exported?
Solved! Go to Solution.
Hey @AhmadBakr,
Looking at your clustered bar chart export issue, here are the practical solutions to control the exported data headers and remove dynamic formatting strings:
1. Create Custom Column Headers Using DAX Measures
2. Build Intermediate Summary Table
3. Remove Dynamic Formatting from Measures
4. Alternative Approach - Use Disconnected Tables
5. Export Control Method
Key Points:
This approach will give you clean, professional column headers in your exported data while maintaining the dynamic functionality of your parameters.
Fixed? ✓ Mark it • Share it • Help others!
Best Regards,
Jainesh Poojara | Power BI Developer
@jaineshp thank you for the detailed suggestion.
The challenge here is that I saw your suggestion very lengthy and will be very hard to maintain.
I reached to another way, and I was testing it... probably this is my reason for not reverting quickly:
End result:
From User perspective:
The dashboard user has a sleek way to choose ANY fact table column, and export them to Excel
From Developer perspective:
- I have full control on the exported data column names, as they are taken from the field parameter table I created.
- And an easy to maintain setup.
Screen shots below:
👈The table/slicer combo. Data export possible from the ellipses
👈 Options in the slicer based on the Export field parameter fields
👈The Export field parameter DAX code.
Note that the first column in the Export parameter table contains the lables of fields, which will be the column headers in the exported data --> developer controlled.
Last 2 columns are used in grouping similar fields to create a heirarchy in the slicer.
This is so, because I noticed that any visual other than the table (and matrix) visual does not contain column headers of course, thus it uses the columns/measures names, and to work around this would require a lot of work which I did not want to do. At the end it is one feature - data export - we are talking about. It does not have to be costly.
Appologies for the delay in responding to your effort.
And to @v-venuppu, I am not sure if I can mark 2 solutions? The only aim is to draw the attention any reader of this issue to the solution I managed in addition to the one suggested by Jainesh. The fact that it is offering a user-controlled export meachnism was very much appreciated by my dashboard users and I want to share the knowledge
Hi @AhmadBakr ,
Thank you for reaching out to Microsoft Fabric Community.
Thank you @jaineshp for the prompt response.
I wanted to check if you had the opportunity to review the information provided and resolve the issue..?Please let us know if you need any further assistance.We are happy to help.
Thank you.
Hey @AhmadBakr,
Looking at your clustered bar chart export issue, here are the practical solutions to control the exported data headers and remove dynamic formatting strings:
1. Create Custom Column Headers Using DAX Measures
2. Build Intermediate Summary Table
3. Remove Dynamic Formatting from Measures
4. Alternative Approach - Use Disconnected Tables
5. Export Control Method
Key Points:
This approach will give you clean, professional column headers in your exported data while maintaining the dynamic functionality of your parameters.
Fixed? ✓ Mark it • Share it • Help others!
Best Regards,
Jainesh Poojara | Power BI Developer
@jaineshp thank you for the detailed suggestion.
The challenge here is that I saw your suggestion very lengthy and will be very hard to maintain.
I reached to another way, and I was testing it... probably this is my reason for not reverting quickly:
End result:
From User perspective:
The dashboard user has a sleek way to choose ANY fact table column, and export them to Excel
From Developer perspective:
- I have full control on the exported data column names, as they are taken from the field parameter table I created.
- And an easy to maintain setup.
Screen shots below:
👈The table/slicer combo. Data export possible from the ellipses
👈 Options in the slicer based on the Export field parameter fields
👈The Export field parameter DAX code.
Note that the first column in the Export parameter table contains the lables of fields, which will be the column headers in the exported data --> developer controlled.
Last 2 columns are used in grouping similar fields to create a heirarchy in the slicer.
This is so, because I noticed that any visual other than the table (and matrix) visual does not contain column headers of course, thus it uses the columns/measures names, and to work around this would require a lot of work which I did not want to do. At the end it is one feature - data export - we are talking about. It does not have to be costly.
Appologies for the delay in responding to your effort.
And to @v-venuppu, I am not sure if I can mark 2 solutions? The only aim is to draw the attention any reader of this issue to the solution I managed in addition to the one suggested by Jainesh. The fact that it is offering a user-controlled export meachnism was very much appreciated by my dashboard users and I want to share the knowledge