I am wondering the optimal setup for the "Include in Report Refresh" feature.
For example: I have queries pulling from an third party API that I use for Vendor reporting. These create Table A and Table B. I then manipulate Table A and B seperately, before appending Table A to Table B (using the Query Editor) into a new query - Table C, which I load into my data model.
I feel like I have 4 options:
I think runs hits the API 4x in total. Once each for Tables A and B (desired behavior), and then twice again for Table C (undesired behvior). Not sure if this bug on Microsofts part, or intended functionality. See link - https://community.powerbi.com/t5/Desktop/Disabling-quot-Include-in-Report-Refresh-quot-Bug-or-featur...
This looks to be a good option, but I am unsure if Table C gets updated with the new data if I disable it's IRR functionality
I think this hits the API twice, but runs the queries sequentially and thereby increasing the total query time. It would be great to run Query A and B.
A backup option for option 2. The downside of this is the DAX can get kind of messy I decide to perform transformations other than a UNION. Plus, it adds bloat to my data model as I need to enable load for A, B plus the DAX Table C
Can anyone shed light on these hypotheses and point me to towards the optimal setup?
"Include in report refresh" option only works for Power BI Desktop, it doesn't impact the refresh process in Power BI Service.
In Power BI Desktop, when you disable "Include in report refresh" option, data will not update in report view of Power BI Desktop after you click "Refresh" button in Desktop.
IF you enable IRR for Tables A and B only
then after you click "Refresh" button in Desktop,table A and B will refresh but table C will not refresh.
IF you enable IRR for Tables C
then after you click "Refresh" button in Desktop,table A and B will not refresh but table C will refresh.