You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have an old toolkit install and are gradually updating. We are currently at the January 2024 update and I noticed that the Unique Launches By User and App visual no longer exists in Nurture > App Usage in the Power BI report. I had requested this visual be added a couple years ago as it was valuable in our usage research.
Expected Behavior
Please add the Unique Launches By User and App visual back to the Power BI report.
What solution are you experiencing the issue with?
Core
What solution version are you using?
4.22
What app or flow are you having the issue with?
Power BI report
What method are you using to get inventory and telemetry?
Cloud flows
Steps To Reproduce
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Hello. I dont recall that particular visual but am happy to put this on the backlog for consideration. Do note that we are quite tied up right now so it will be a while.
If you go about implementing it again yourself do let us know and share!
Does this bug already exist in our backlog?
Describe the issue
We have an old toolkit install and are gradually updating. We are currently at the January 2024 update and I noticed that the Unique Launches By User and App visual no longer exists in Nurture > App Usage in the Power BI report. I had requested this visual be added a couple years ago as it was valuable in our usage research.
Expected Behavior
Please add the Unique Launches By User and App visual back to the Power BI report.
What solution are you experiencing the issue with?
Core
What solution version are you using?
4.22
What app or flow are you having the issue with?
Power BI report
What method are you using to get inventory and telemetry?
Cloud flows
Steps To Reproduce
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: