-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CoE Starter Kit - Feature]: Add link to app and flow details page to Power BI dashboard #6793
Comments
Great idea, thank you for raising this! We do have some links in place to take you to the Power Platform Admin Center but not to take you to Flow/App details pages. We'll add this to our backlog. Thank you for using the CoE kit! |
This will require either bringing in the env variable so we know what url to use or adding another input parameter. |
Adding a parameter for this is doable but we dont currently collect everything we need to make the links for MDA's. So moving to Feb so we can add that too. |
need to add a few fields in the sync flows to get this to work for MDA |
@smwill365 This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us. |
1 similar comment
@smwill365 This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us. |
Hi, |
Is your feature request related to a problem? Please describe.
The problem is locating flows and apps found in the coe starter kit.
Describe the solution you'd like
Within the starter kit Power BI report. Please include a clickable link within tables to take you directly to the app, flow, etc.
Describe alternatives you've considered
No response
Additional context?
No response
AB#915
The text was updated successfully, but these errors were encountered: