Forum Discussion
Dataflows deployed from a Deployment Pipeline - invalid data source
- 4 years ago
I have reported this issue through a Power BI Support ticket, and it has been acknowledged as a bug which involves the Data Flow team, the Lineage team, and the Deployment team. The estimated time the bug will be resolved is Feb 2022.
I have been able to work around this issue partially by parameterizing the database and server names in the connection, and using deployment rules on the parameter values in the deployment. In the target workspace, the old data source dependency is shown in the lineage view, but that "phantom" data source does not need to be mapped to a data gateway in the settings of the data flow.
When I didn't parameterize the data source server and database, I needed to map the "phantom" data source to a data gateway (and the same data gateway) as the valid data source.
I have reported this issue through a Power BI Support ticket, and it has been acknowledged as a bug which involves the Data Flow team, the Lineage team, and the Deployment team. The estimated time the bug will be resolved is Feb 2022.
I have been able to work around this issue partially by parameterizing the database and server names in the connection, and using deployment rules on the parameter values in the deployment. In the target workspace, the old data source dependency is shown in the lineage view, but that "phantom" data source does not need to be mapped to a data gateway in the settings of the data flow.
When I didn't parameterize the data source server and database, I needed to map the "phantom" data source to a data gateway (and the same data gateway) as the valid data source.