Currently...To get this information, I have to run multiple admin api's, including Get Datasources for each dataset. This takes 10 hours to run through all of our datasets in the tenant. Then I have to map it to the output of Get Datasources for the gateway. I am afraid to just let the 10 hour job run unattended, so I break it up in to workable time segments, which requires this to be a manual process. It is only something that can be done every quarter at best. We can see in the workspace lineage views on the tenant that the data is already linked and available, so please expose the same linkage view from the gateway connection perspective.
Additionally adding "last time used" attribute on the Get Datasource Status api or in the proposed new lineage view, would help us identify inactive connections that are still attached to datasets not being refreshed. I have tried to use the actual gateway logs from the servers, but this only exposes active connections. I have to manipulate the output to throw into Excel and perform vlookups for the connections that don't show up and assume they are inactive from a very limited point of time captured in a log file.
In summary, Administrators don't have time to come up with adhoc solutions such as this and would GREATLY benefit from this view. I know how voting works and this won't even be reviewed most likely. There aren't enough Admins to increase the votes. :(
Recent ideas
Visual header icon improvements: Options for permanent visibility on per-icon basis, weblinks etc.
Current problem: Visual header icons like the 'Help tooltip' icon are potentially incredibly useful, however they rarely pass muster for our needs as so many of our report owners/authors insist on th...
