Forum Discussion
Helper IIWhat to do when developers leave an organization?
Helper IIThanks, TomMartens and lbendlin--I agree with your process and technical suggestions. The challenge here is that there are dozens of reports connecting to very many SharePoint document libraries. For context, each department (e.g. Finance, Operations, etc.) has its own document library. It then becomes impractical to have an admin create a service account to connect to each library. There could be a global service account with access to all document libraries, but that would be too powerful to give to report publishers. The double admin idea is solid but refreshes would still fail if a publisher leaves the company.
Another proposal is to run a script to replace all data source credentials for the exiting employee with the credentials of the employee who will be taking over the semantic models, etc. However, I am not certain if the API allows this for all artifacts.
Super UserThe API allows that in a very convoluted way ( you need to run multiple calls in a specific sequence) but that is missing the point. The employee leaving should be an inflection point and and opportunity to review if these datasets are still needed or can be retired.
- asocorrocognex
Perhaps you are right and there is no automated way (via API calls or service accounts) to prevent or recover from these failed refreshes, and the only solution is an orderly employee exit process, when possible.
- aj1973
Community Champion
Easiest way would be the new Admin of the wrokspace takes over the semantic model and configure credentials.
