Forum Discussion
Versioned fact table report
Anonymous
1. Possibly our prefered option is direct connect, so any tricks in the loading is not relevant in that case.
You can still do this with DirectQuery depending on what your data source is. If it is sql server then you can take advantage of query editor even with directquery.
But yes agree if rules are going to be complex and easy to implement via source do it that way (saying that you can still do it via power bi but depends on how complex rules are).
Anonymous
In Power BI Desktop, it only takes the data from data source and render it. It doesn't support versioning. For your scenario, I don't think there's other way than using snapshot tables.
Regards,
Anonymous Since you only want 20th of each month in power bi desktop when you import data via query editor you can extract out date into a seperate column and then set that new column to be 20 via filter. That way you only looking at 20th of each month.
ankitpatira thanks for the suggestion. But I think this is not going to be a solid solution, so I assume the answer will be a NO. The snapshot fact table will have to be maintained in the database - which is not a big deal if that is the case.
Reasons:
1. Possibly our prefered option is direct connect, so any tricks in the loading is not relevant in that case.
2. The actual rule for the snapshot could be much more complex than the 20th each month. Could be varied each month etc.
Anonymous
1. Possibly our prefered option is direct connect, so any tricks in the loading is not relevant in that case.
You can still do this with DirectQuery depending on what your data source is. If it is sql server then you can take advantage of query editor even with directquery.
But yes agree if rules are going to be complex and easy to implement via source do it that way (saying that you can still do it via power bi but depends on how complex rules are).