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 IVActually, I didn't check it on the right place. My access right to the dataset at Test Workspace is as Administrator/Owner ("Proprietário" in Portuguese):
Power BI Teamadditional option is that the dataset is only connected to Power Bi artifacts, such as dataflows, and not to external data sources. Can you specify which data sources are this dataset connected to?
- trt18-sistemas
Hi 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).- Nimrod_Shalit
trt18-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.