Forum Discussion
Advocate IVDataset parameters disabled (greyed) at Pipeline
Posting the solution.
On my example, the parameter data type is set as "any" (qualquer in portuguese). By setting as "text" it worked.
As simple as that .... rsssss
Advocate IVHi Nimrod_Shalit,
At this simple example it's not connected to any datasource. I've created a table as mention on my first message.
On my real world case, where I'm facing the same problem, I'm connected only at dataflows. I'm using textual parameters to define the name of at which workspace connect to (it's not a connection parameter).
Power BI Teamtrt18-sistemas,
When you are connecting only to a Power BI artifacts, such as dataflows, we will handle the connections across WSs for you. no need to setup rules.
See more here- Deployment pipelines, the Power BI Application lifecycle management (ALM) tool, process - Power BI | Microsoft Docs
Please remove the parameter from the connection, as it probably disrupts the auto-bind process to happen.
- trt18-sistemas
Hi Nimrod_Shalit,
Reading the link you sent to me, it seems that it was suppose to work, as written at https://docs.microsoft.com/en-us/power-bi/create-reports/deployment-pipelines-process#auto-binding-and-parameters. But, diving deeper into this subject I found this https://docs.microsoft.com/en-us/power-bi/create-reports/deployment-pipelines-get-started#deployment-rule-limitations. The 7th item says: "Rules for datasets that use dataflows as their source, are not supported.", which is excatly my case. My dataset has only one data source which is a Dataflow hosted in a different worspace.
- trt18-sistemas
Trying to solve my problem, I tried to implement a similar solution recommended here https://docs.microsoft.com/en-us/power-bi/create-reports/deployment-pipelines-process#avoid-using-auto-binding.
- I connected my dataset to my production Dataflow (hosted in a different workspace, that has no pipeline implemented), removind all parameters concerning to data source connections;
- Published my Dataset at Workspace [Dev];
- Connected my Paginated Report to the Dataset published at Workspace [Dev] and publised it at the same workspace;
- Using pipeline, deployed Dataset + Report + Paginated Report to Workspace [Test];
- Using pipeline, deployed Dataset + Report + Paginated Report to Workspace [Prod];
- Tried to access Paginated Report at Workspace [Prod] , but I encouter a error (picture 1 bellow);
- Downloaded Paginated Report from Workspace [Test] and checked its connection, then I found out that it's connected to the Dataset from Development Workspace (picture 2 bellow), which means that Autobind Pipeline didn't work.
Picture 1) error trying to open Paginated Report at Workspace [Prod]
Picture 2) Autobind on Paginated Report deployed at Workspace [Test] didn't work and kept the connection to the Dataset at Workspace [Dev].
Any suggestion on how to make pipeline works on this scenario?
- Nimrod_Shalit
- Still not sure why are you trying to use a rule for the dataflow-->dataset connection. What's the use case where you need a rule and not the auto-binding?
- As for the paginated report not being auto-binded to the dataset in Test, this sounds like a bug, and you should open a support ticket so we can further investigate.