Forum Discussion
Pipeline & data refresh issues
Hi , lhuynh
In the target stage, item properties that are not copied, remain as they were before deployment. New content and new items are copied from the current stage to the target stage.
The following dataset properties are also not copied during deployment:
-
Role assignment
-
Refresh schedule
-
Data source credentials
-
Query caching settings (can be inherited from the capacity)
-
Endorsement settings
For more information, you can refer to :
Deployment pipelines, the Power BI Application lifecycle management (ALM) tool, process - Power BI | Microsoft Learn
Thank you for your time and sharing, and thank you for your support and understanding of PowerBI!
Best Regards,
Aniya Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Hi Aniya,
I have entered the exact credentials that worked at development into test and it doesnt not accept them.
- v-yueyunzh-msft3 years agoCommunity Support
Hi, lhuynh
According to the screenshot you provided, I found the corresponding error message "The OAuth authentication method isn't supported for this data source" on the internal problem website and has been submitted to the product team. ICM number: 349438899.
Research on this issue is still ongoing in collaboration between product groups and technical engineers, so I'll keep you informed if there are any updates.
Thank you for your time and sharing, and thank you for your support and understanding of PowerBI!
Best Regards,
Aniya Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
- lhuynh3 years agoRegular Visitor
Hi Aniya,
Sorry could you clarify, the OAuth authentication works at development but when deployed to test it doesnt work. Is this a system bug that needs to be fixed?
- v-yueyunzh-msft3 years agoCommunity Support
Hi , lhuynh
Yes, this is strange,it works in your development and not work in test. But according to your error message, there is indeed a corresponding BUG, for your problem, I recommend that you open a support ticket for in-depth troubleshooting.If you are above a Power BI Pro licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you.
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.
The link of Power BI Support: https://powerbi.microsoft.com/en-us/support/
For how to create a support ticket, please refer to https://community.powerbi.com/t5/Community-Blog/How-to-create-a-support-ticket-in-Power-BI/ba-p/6830...
Best Regards,
Aniya Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly