Matthew Wainwright on 11 Dec 2018 17:46:00
The refresh failure notifications only contain the name of the affected dataset. Sometimes datasets in different workspaces can have the same name, including the workspace name in the e-mail would make troubleshooting much easier
- Comments (5)
RE: Include workspace name in refresh failure notifications
Will be very helpful. In some cases, you do get failure notification, but you have not access to that workspace = URL to dataflow is useless, so no easy way to understand which workspace hosts that dataflow.
RE: Include workspace name in refresh failure notifications
I just logged in to suggest this idea. Especially now that the deployment pipelines feature explicitly endorses the concept of deploying multiple copies of the same objects across many workspaces.I would add that it would be helpful to also have the subscription name in the notification. In my situation, we have the same named datasets deployed to multiple workspaces in multiple subscriptions.Thanks,Craig
RE: Include workspace name in refresh failure notifications
This is real problem for us, since we have the same object names (such as dataflows, datasets, etc.) in each workspace, so when we get an error message, we have to check every workspace.
RE: Include workspace name in refresh failure notifications
This is a great idea. Would love to see this functionality added.
RE: Include workspace name in refresh failure notifications
Agreed. Our company has several different Workspaces for different regions (Houston, Calgary, London, Perth, Kuala Lumpur).
Each contains the same equivalent Dataflows and Entities with the same exact names (eg. Sales, Purchases, etc.).
When a Refresh fails and we receive the Email notification, it only says the Refresh failed for Sales.
It would be very helpful to see in the email notification that the Refresh failed for Sales in the Houston Workspace, preferably in the Subject of the Email.