Handle data connection updates without forcing recreation of content

[jayme_edwards1]

In the online version of power bi, if you change the account the SSAS connector runs under, the connection in powerbi becomes cached and cannot be updated. Additionally, changing servers from for example one Azure server to another breaks the connection. For Enterprise customers to use power bi, it is necessary for us to be able to point existing data connections to new configuration locations. Without this capability, if we move SSAS servers or change the account that the connector runs under, we have to manually create a new connection for all of our users and they must re-create their content that used the old connection!

[Bjoern]

Definitely useful feature. The whole "connect to" is pretty limited for AS tabular. Would be nice to have it the same way, as it is already implemented for SQL sources.

[sid4]

This is a definite need - clients of ours will change servers, process accounts, but not the model and the connector should be resilient enough to handle those changes without users losing all their connections and content

[sqlltedt]

Testimonios

[demo6]

Test

[demo6]

Test

[demo6]

Test

[demo6]

Gbbzh

[nnmbhalati]

This is a must!

[kdelmotey]

is this limitation for all data sources or just SSAS ?

[ga9286]

i believe its really necessary, maybe this will be a feature for Power BI Pro.