Forum Discussion
Feature usage and adoption not working
- 1 year ago
Hi twiek
We finally figured it out... there's a section in the documentation that talks about reinitializing the admin workspace.
These were the steps we took to finally fix the app:
- Logged into Fabric
- Navigated to the Admin Monitoring workspace
- Captured the Workspace Id
- Opened up developer tools in the browser, navigated to the network tab, and filtered on Fetch/XHR. Then refreshed the page so we could grab the bearer token (it's a short-cut we use to get a bearer token when using something like Postman). Any fetch request should have the bearer token in the headers... so just pick one (in the image here I picked base), and then on the right, under "Headers" you can scroll down to find the bearer token under authorization.
- Then we used postman to make a DELETE call to the endpoint from the Microsoft article using the Workspace Id and bearer token (just toss the bearer token under Authorization). I'm not sure how familiar you are with Postman, but if you have any questions just let me know. You should get a 200 back if the delete is successful.
- Went back to the browser and refreshed the page... It basically reinstalls the admin workspace apps. Then it will refresh the underlying semantic models. And in about 15 minutes our usage app started working again.
No idea why Microsoft has made this such a convoluted process. The fact someone has to use the underlying APIs to fix their broken apps is just absurd IMO. Great job w/ the usability there Microsoft.
Hope this helps. If you have any questions or run into any problems just let me know.
Hi johnbasha33 and thanks for your answer. However I can't check any of your first 3 suggestions properly as there is no possibility to access any kind of settings of this particular dataset. Settings as known from other datasets like gateway connections / data connections in general do simply not exist for this feature.
1) I can only see the last refresh, I can't find a history
2) If I could see anywhere which connections are necessary I could do that
3) The gateway definitley works for all other reports
Maybe I just can't find the settings and you can help me there? Or anybody has had a similar problem?
Thanks
- jeremycolson11 year agoAdvocate I
Hi twiek - did you find a solution for this? We have run into the same problems and like you noted, access is so restricted to this workspace we cannot do anything to diagnose or attempt to resolve.
- twiek1 year agoFrequent Visitor
Hi, unfortunately I did not resolve this and I couldn't find any solution on the web or AI... I am still interested in a solution.
- jeremycolson11 year agoAdvocate I
Hi twiek
We finally figured it out... there's a section in the documentation that talks about reinitializing the admin workspace.
These were the steps we took to finally fix the app:
- Logged into Fabric
- Navigated to the Admin Monitoring workspace
- Captured the Workspace Id
- Opened up developer tools in the browser, navigated to the network tab, and filtered on Fetch/XHR. Then refreshed the page so we could grab the bearer token (it's a short-cut we use to get a bearer token when using something like Postman). Any fetch request should have the bearer token in the headers... so just pick one (in the image here I picked base), and then on the right, under "Headers" you can scroll down to find the bearer token under authorization.
- Then we used postman to make a DELETE call to the endpoint from the Microsoft article using the Workspace Id and bearer token (just toss the bearer token under Authorization). I'm not sure how familiar you are with Postman, but if you have any questions just let me know. You should get a 200 back if the delete is successful.
- Went back to the browser and refreshed the page... It basically reinstalls the admin workspace apps. Then it will refresh the underlying semantic models. And in about 15 minutes our usage app started working again.
No idea why Microsoft has made this such a convoluted process. The fact someone has to use the underlying APIs to fix their broken apps is just absurd IMO. Great job w/ the usability there Microsoft.
Hope this helps. If you have any questions or run into any problems just let me know.