12-11-2020 08:35 AM - last edited 12-11-2020 08:36 AM
(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.
@AbrahamSaldanaThanks for all the great work on this solution!! The new version 1.3 fixed my issue.
Thank you, Abe!
I have updated the apps today, but now I'm having another type of error:
FACILITY MANAGEMENT Version 20
Processing error: The key didn't match any rows in the table.
Cluster URI: WABI-WEST-US-redirect.analysis.windows.net
Activity ID: 0be42905-746b-4d54-a103-41652f07058f
Request ID: 85ffd0c5-e8d0-bc89-a2dd-23eaafcea2c3
Time: 2020-12-09 13:18:16Z
LOCATION READINESS Version 16
Processing error: The key didn't match any rows in the table.
Cluster URI: WABI-WEST-US-redirect.analysis.windows.net
Activity ID: 0be42905-746b-4d54-a103-41652f07058f
Request ID: bfc22bd8-02e8-8c6d-d6ed-a06eb4bef95c
Time: 2020-12-09 13:24:32Z
I know that this type of error in Power BI might happen when you work with a cashed dataset. I have refreshed from the browser, InPrivate, and also used a different browser, but the result is the same.
What can I try to fix it?
Thanks!
~Alienvolm
what you need to do is to re-deploy the dashboards and then embed the Facility Management dashboard again with the new dashboards ids and groups, you will need to deploy the dashboards for release 1.3, the dashboards will create a new workspace.
Hello, that worked, thank you!
Now I have another problem though... I'm trying to Embed the Power Bi report in the model-driven app - step 5 of the procedure:
On step 2, I don't see any entity called "Facility" and I do not see any of the tabs on top of the blade (Forms). This is what I see instead:
What am I missing?
Thanks again!
~Alienvolm
when adding the Table to the solution you select the facility, and after that you select all items on the entity, then will show all the forms and views and all entity elements you need to do the embedding.
Other option is to use the XRMToolBox with the Power BI embedder plugin
abe
Hello Admin, after the recent upgrade to version 1.3, users are unable to access the app and see the attached error. There are various messages that are being displayed at the top. However, when I try to access the app as a Global Administrator, I don't see the issue. Could you please let us know if there are any access settings that we need to configure as part of the latest upgrade?
Thanks for connecting and sharing, I will connect with you directly and we can get more details on the issue and share when is fixed.
Abe
For the upgrade to v1.3 the article mentions that the upgrade impacts user experience. I am wondering what gets impacted when compared to v1.2 for the ‘Employee Return to Workplace App’?
Does the upgrade impact the UI, variables or custom tables or data that was modified? It would also be nice to hear if anyone tried the upgrade and what their experience was with it.
Looks like we might have a schema change issue again. I'm on version 1.3. The PowerBI refresh failed last night with this error:
"The 'bottom' column does not exist in the rowset"
Is anyone else seeing this issue?
Diver7 thanks for letting us know, we encountered the issue yesterday and we are working on that schema change we will provide a short hotfix soon!
Thanks!
Abe