Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago
Solved

Incomplete data for Table.Combine when sourced from Incremental Refresh

We are using Table.Combine to append two data sources which both use incremental refresh. As such the row count of the child table must match that of the two parent tables.   When the dataset is pu...
Need Help
  • Anonymous's avatar
    Anonymous
    5 years ago

    Hi Kelly,

    Apologies, when I mentioned row count I meant as the result of the DAX count aggregator of the resulting tables after data refresh has completed.

     

    I am not experiencing a technical error using Combine.Table.

     

    The M query is also the same as what you have in your example. The only exception, I imagine, would be that my parent tables are configured for incremental refresh.

     

    I have also investigated further and seems that Combine.Table evaluates the parent tables based on the default filter parameters for incremental refresh (RangeStart and RangeEnd). As such it seems like it doesn’t matter what the volume of data that resides in the model as this is evaluated on Power Query first.

     

    I have also tested calculating a DAX table while using UNION and this does give the correct row count. This also seems reasonable as the evaluation of DAX refreshes comes after Power Query is complete (and other incremental refresh).

Anonymous's avatar
Anonymous
Not applicable
5 years ago

Hi Kelly,

Apologies, when I mentioned row count I meant as the result of the DAX count aggregator of the resulting tables after data refresh has completed.

 

I am not experiencing a technical error using Combine.Table.

 

The M query is also the same as what you have in your example. The only exception, I imagine, would be that my parent tables are configured for incremental refresh.

 

I have also investigated further and seems that Combine.Table evaluates the parent tables based on the default filter parameters for incremental refresh (RangeStart and RangeEnd). As such it seems like it doesn’t matter what the volume of data that resides in the model as this is evaluated on Power Query first.

 

I have also tested calculating a DAX table while using UNION and this does give the correct row count. This also seems reasonable as the evaluation of DAX refreshes comes after Power Query is complete (and other incremental refresh).

  • v-kelly-msft's avatar
    v-kelly-msft
    Community Support
    5 years ago

    Hi  Anonymous ,

     

    Yes,after testing,Table.Combine can only combine source tables,once I use the filtered table,it will return error：

    So the method you mentioned above should the best solution.

    If your issue is solved,could you mark the reply as answered to close it?

     

    Best Regards,
    Kelly

    Did I answer your question? Mark my post as a solution!