Forum Discussion
Incremental Refresh Using Stored Procedure, Parameters Not Overridden in Power BI Service
correct. They don't know anything about the query that runs on that table. Don't use them, find another way, for example via the data model.
I found this workaround. Re: incremental refresh on table by reference - Microsoft Fabric Community , which fixes the issue by passing the incremental refresh parameters to dummy variables in the reference table queries. With the dummy variables in the reference queries, Incremental Refresh configurations can be applied (there will be a warning that query folding can't be confirmed). After publishing and refreshing, all tables now have partitions and the correct amount fo data.
How many partitions have been created for that table?
Good prompt. I connected via SSMS to the XMLA endpoint and saw that the table loaded from the SP actually does have multiple partitions and the correct amount of rows. This table is hidden in my semantic model because it is a staging table for two other tables that use it as a referenced source. Both of these tables have no partitions and only have data for the one day. It seems that reference tables do not "inherit" the incremental refresh settings from the source table?
correct. They don't know anything about the query that runs on that table. Don't use them, find another way, for example via the data model.
Thanks, this knowledge helped me to discover a workaround.