Rename a dataset or dataflow as part of pipeline rule?

[Guillaume_]

When deploying a dataset or a dataflow through a pipeline rule there is no way at this point to rename / prefix / suffix the object name?

This would help to maintain distinct names for clarity, ie 

DEV Sales Analysis -> TEST Sales Analysis -> Sales Analysis

At the moment the object has the same name and the only way to differentiate is the workspace name which may lead to confusion.

[Guillaume_]

Thanks but I'm after changing the name of the object ie the dataset or the dataflow.

I've actually noticed that it can be renamed after deployment and the relationship between source and destination seems to be maintained.

Therefore it could be just a simple operation as part of the first deployment.

[niekkremers]

I'm still running into the problem that, after renaming, a change is detected by the deployment pipeline. The connection between the object and the renamed object is indeed there, however, when deploying, a change (in name) is discovered, which in turn will be deployed by the pipeline. 
That is: the name in the destination stage is changed back, according to the name in the source-stage.. 

Is there anyone who has a solution to this issue?

[v-jianboli-msft]

Hi @Guillaume_ ,

According to my knowledge, if you want to change the name of datasource in pipeline, you may need to change the data source connection.  You can’t change the data source connection in pipline stages in Power BI service.

If you want to change the data source in the test or production stages, you can use deployment rules or APIs. Deployment rules will only come into effect after the next deployment.

For more details, please refer to:

Get started using deployment pipelines, the Power BI Application lifecycle management (ALM) tool - P...

Troubleshoot deployment pipelines, the Power BI Application lifecycle management (ALM) tool - Power ...

Best Regards,

Jianbo Li

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Guillaume_]

i'm after renaming the object not the connection. At the moment we have to manually rename objects po-deployment. I assume this should be a fairly simple rule to be built in deployment pipelines.

[filip_ai]

I too have this problem. I think it makes sense to have the environment name added to e.g. the semantic model or (paginated) report file - or at least have the flexibility to do so. To be able to parameterize the destination name would be great.