Forum Discussion
Return value based on time-stamp
- Anonymous2 years ago
Hi 123CaM321 ,
Regarding your question, is your connection mode Direct Query? After using DAX to create a calculated column, the query is sent to the data source, the data source returns all the data, and finally filtered by DAX. This may be the reason for the poor performance. You mentioned that you plan to implement it in Power Query. Please make sure that the steps applied support query folding, which will reduce the amount of data returned and thus improve performance.
Best Regards,
Wenbin Zhou
Hi 123CaM321 ,
Regarding your question, is your connection mode Direct Query? After using DAX to create a calculated column, the query is sent to the data source, the data source returns all the data, and finally filtered by DAX. This may be the reason for the poor performance. You mentioned that you plan to implement it in Power Query. Please make sure that the steps applied support query folding, which will reduce the amount of data returned and thus improve performance.
Best Regards,
Wenbin Zhou
Thanks for the reply. I am using a query and importing. I'm not finished testing yet, but what I've done is, join the tables in power query then use the fill down transformation to fill in the gaps. This adds TableB[VALUE] to every time point in TableA. So far from what I've seen, it is far more efficient manipulating the data this way.
I probably could have constructed a query that would have skipped the join, but this works. Will report back