Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
Hello,
We are working on paginated reports within Power BI Report Builder and some of the report tables will include a LOT of data points. We prefer not to include all of these data points as column headers within the table because the table would become very wide and may not be usable once converted to Accessible PDF, which is also something we need to be able to support. To accommodate this, our BI team wanted to "section" the data so that some of it appears above the table as depicted in a test table below:
Note: The example table above only shows 9 columns but we have some reports that could have up to 22.
So basically you have some "sectioned" data on top of the table (e.g., Dept, Dept Unit, Fund, etc.) and then a classic data table below it. The problem we're encountering is that the "sectioned" data above the table is included within the <table> markup that gets generated within the Accessible PDF, which is incorrect from a PDF tagging perspective and results in incorrect TH/TD cells counts within each row of the table. Since these will be automatically generated PDFs, we don't have the ability to manually edit the markup to our preferences. Our Power BI team also says that this "sectioned" data MUST be part of the table within the Report Builder tool in order to generate the table properly (i.e., there is no option to try to separate out the "sectioned data" to prevent it from being included in the PDF <table> markup).
Is there any way to somehow designate in Power BI Report Builder that the "sectioned" content should NOT be included in the table tagging for the resulting Accessible PDF? Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.