(Updated 9/9/2020)
Hi Team,
We’re delighted to announce v1.1 of the Power Platform Return to the workplace solution. We’ve heard your feedback and incorporated many of the requirements our customers have been asking for with this release. The new solution will be released on AppSource today. Summary is here but please also see below for more details.
APSOURCE REL 1.1 links
App
Power BI
Location Readiness Dashboard
https://aka.ms/rtw-leadershippbi
Workplace Care Management Dashboard
https://aka.ms/rtw-workplacepbi
Facility Management Dashboard
https://aka.ms/rtw-facilitypbi
*****************Original Post***********************
Reopen responsibly, monitor intelligently, and protect continuously with solutions for a safer work environment. Equip facility managers and task force leaders to make informed decisions to safely reopen locations. Empower employees to return confidently with self-service tools for working safely and productively. Help health and safety leaders ensure the care and well-being of your workforce.
Learn more about the solution , watch the video and read the documentation to understand capabilities and working with the solution.
@PMLIO Hi! Try following these steps (they were listed earlier by another user, and worked for me)
1-Go to Power Apps, select Solutions in the left pane, and create a new solution with name like "Facility".
2-Open the newly created solution, select Add existing, and then select Entity.
3-From the list of entities, select Facility > select components.
4-Under the Forms tab, select the item with Display Name of "Information" and Form Type of "Main".
5-Click "add" until you are back at the Solutions > Facility screen.
6-Publish all customizations at this point and then Export as "unmanaged".
7-Edit the customizations.xml file within the exported zip.
8-You should find a <section> shortly after the <FormXML> that looks identical to the code snippet called out in the "embed" link of Step 5.5.
9-Launch your "Return to Workplace - Facility Manager" PowerBI report to find your GUIDs within its URL.
URL formatted as follows -> https://app.powerbi.com/groups/<PowerBIGroupId>/reports/<PowerBIReportId>/
10-Replace the GUIDs within that section with the corresponding GUIDs of your deployed "Return to Workplace - Facility Manager" PowerBI report.
11-copy changes back into your zip.
12-upload and publish.
This is a clever solution that is quick to deploy, but the Power BI reports don't seem to have been designed with accessibility in mind. In the Power BI reports, I can see that tab order isn't set, there is no alt text set, and there are color contrast issues. There are also a couple of spots where color is used as the only indicator of meaning, which doesn't work for users with color vision deficiency or low vision. I admit I'm not super proficient with a screen reader, but trying to navigate the Power App canvas app was a bit frustrating, so I think there might be issues there as well. But the color contrast on the Power App is good.
It would be great to see the issues corrected in the Power BI apps for the next release. Happy to help if needed.
@PMLIO Hi! Try following these steps (they were listed earlier by another user, and worked for me)
1-Go to Power Apps, select Solutions in the left pane, and create a new solution with name like "Facility".
2-Open the newly created solution, select Add existing, and then select Entity.
3-From the list of entities, select Facility > select components.
4-Under the Forms tab, select the item with Display Name of "Information" and Form Type of "Main".
5-Click "add" until you are back at the Solutions > Facility screen.
6-Publish all customizations at this point and then Export as "unmanaged".
7-Edit the customizations.xml file within the exported zip.
8-You should find a <section> shortly after the <FormXML> that looks identical to the code snippet called out in the "embed" link of Step 5.5.
9-Launch your "Return to Workplace - Facility Manager" PowerBI report to find your GUIDs within its URL.
URL formatted as follows -> https://app.powerbi.com/groups/<PowerBIGroupId>/reports/<PowerBIReportId>/
10-Replace the GUIDs within that section with the corresponding GUIDs of your deployed "Return to Workplace - Facility Manager" PowerBI report.
11-copy changes back into your zip.
12-upload and publish.
@narpad hi, these are the exact same steps as in the document right? But there is no Titleurl to ammend?
I followed Step 5: Embed the Power BI report in the model-driven app to the letter - created the 'Facility' unmanaged solution --> exported --> customised --> Imported . Then opened the Facility Safety Management app and clicked on New. Then this is what I get. I sign-in then go through the motions then back to this sign-in - rinse & repeat. So I re-exported the 'Facility' unmanaged solution and had a peek in the Customizations.xml file and the PowerBIGroupID, PowerBIReportID and TitleURL are all different. Its as if my customisation is not sticking. Not sure what's going on, it can't be this difficult can it?
My customisation
Another issue, why am I getting this error. The app works but get this error. This is a standard user account who is a member of the 'Return to the Workplace - Employee' group.' If I log on with my admin account I dont get this error.
We had the same issue at my organization, looks like every user of the employee app needs to have a PowerApps license too. I think we first did 30 days trial for everyone
The account I'm using to test has Power App per User license but still get this permissions issue. But if I ignore it, the app works but I don't want to roll out an app like this.
@PMLIO @Anonymous
This was an issue which was discovered to late unfortunately, the Return to the Workplace - Employee role needs organizational read, create, update, append and appendto rights. This will be fixed in the next version.
Thanks for your feedback on the Power Bi Dashboards, The Return to Workplace passed and has been verified for Accessibility and compliance, we are going to take your feedback and validate these recommendation.
abe
This will be the workaround before we get this fix on the next release
Please edit the Security role, and select Custom Entities tab.
Select the Entity "Daily Occupancy" and add organizational privilege's to all the options except Delete.
Abe