Forum Discussion
Reports don't work post deploying from DEV to UAT using Deployment Pipeline
I do agree the Query folding happens in the Power Query Editor and we have not applied any query folding in our Power Query Editor.
Yes we have connection details paramters defined in the Dataflows, pointing to these Dataflows the common Dataset(Semantic Model) is created.
Inside dataset we perform basic transformation like join, append, remove or add columns.
And no, as one workspace can be assigned only once, we have used this workspace in only one pipeline. But we do have different pipeline for different workspaces.
The issue is not only for one visual, it's happening for various visuals except the places where Python script visuals is used.
visual breaking here are normal TABLE visual
So if you download the report in UAT you can confirm it is connected to the dataset you expect it to be connected to?
Generally this seems to be hitting the limitations of DirectQuery by what you are doing inside the report, maybe month ending is a calculated column or so.
Make sure to read through the limitations and then analyze what could be the cause. It could be your data model or a calculated column or something with Auto Date/Time?
- PRAVISH_SARAVAN2 years agoFrequent Visitor
sure, will go through the shared link on DirectQuery Limitations.
Also, the MonthEnding is not a calculcated column, it's pulled form the created Dataflow.The strange reason was, until last friday(3/11/2023), the reports and deployments were wokring fine, starting this monday(6/11/2023) the reports started to not load the visual in TEST workspace.
Was there any new release happened over last weekend? Could that be possible route cause, if so any release udpate we can expect this weekend?