Forum Discussion
Deployment Pipeline Calculated columns
Trying to understand Deployment Pipeline.
Pushed changes from test to Prod via deployment pipeline, I noticed Calculated columns got recalcualted.
Was able to notice it as the column is based on Today() dax and it got changed to the day I pushed the changes, not the day data was refreshed (which was a week ago).
Is this normal function or a bug?
That's what I would expect. If you don't actually want today, then maybe you can take a MAX over one of the date columns in your dataset instead.
7 Replies
That's what I would expect. If you don't actually want today, then maybe you can take a MAX over one of the date columns in your dataset instead.
Strange, because when I deploy from Dev to Test and Dev has a new calculated column, it is NOT calculated in the Test... The visual shows error
Hi,
This is not a known issue. Please open a support ticket for us to investigate it.
Thank you,
Lee
AlexisOlson Thanks for the confirmation. Unfotunately I can't use max date, would you know if I move the calculated column to Power Query side (DateTime.LocalNow ) if the same thing would happen? Would the column get re-calculated in power query if deployed via deployment pipeline?
It would use the time when the query was refreshed. I'd guess that the query would be refreshed during deployment.
Maybe you can create a dataflow that both test and prod connect to so that they can both be in sync?
Thanks for the confirmation again. Going to just put Today() in the source side since data from there does not aut-refresh when deployed using deployment pipeline.
