Skip to main content

Power BI

Needs Votes

Handle data connection updates without forcing recreation of content

Vote (353) Share
Jayme Edwards's profile image

Jayme Edwards on 19 Jan 2016 05:28:11

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!

Comments (14)
Jayme Edwards's profile image Profile Picture

5e16a3f9 c2e7-4f03-995c-1b3c1d222822 on 05 Jul 2020 22:14:55

RE: Handle data connection updates without forcing recreation of content

Testimonios

Jayme Edwards's profile image Profile Picture

55e90c01 fb03-45e7-a78a-5df3a9bf4fae on 05 Jul 2020 22:14:54

RE: Handle data connection updates without forcing recreation of content

Test

Jayme Edwards's profile image Profile Picture

1e8f1ba7 3149-46fa-ae5a-668d7016c8e6 on 05 Jul 2020 22:13:58

RE: Handle data connection updates without forcing recreation of content

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.

Jayme Edwards's profile image Profile Picture

f1d29f17 84b4-45af-8d2c-47fa2987875f on 05 Jul 2020 22:13:58

RE: Handle data connection updates without forcing recreation of content

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