20
Hi,
I have had three people creating guides in the PC App. Everyone could see all the guides in the PC App under the 'All' options, and any they have opened and amended in the 'Recent' option.
Now when we go in we can only see some of the Guides in the 'ALL' option. We can see them all in the 'Power App - Sandbox' link.
Has something changed this week in guides or is there a setting to allow all 'Author's' to see and amend all guides?
Thanks
Paul
Hi Paul,
Several things might explain this behavior and I would start by auditing your security setup.
How are you controlling access to the guides? For example, have you assigned the Author role to your users (see docs)? By default such authors have access to all guides in an instance. If they have a restricted role instead (described here), that would explain why your authors can only see some guides. Users with the restricted author role can only see guides they have created or been shared with them.
If that looks good, check your security group(s) membership. To Ken's point, IT security changes can propagate down.
If that looks good, as a long shot, make sure the guides haven't been deactivated. A deactivated guide won't appear in the PC app but it will appear under the Inactive Guides view on the portal. You can reactivate them if accidentally deactivated.
We did deploy an update this week but that should not have affected your existing instance. But let me know if you or an admin upgraded your CDS instance so I can pull in the right people to help investigate.
Hi,
We are using HL2, but this is without actual using the Holo Lens, just looking at the PC App and the Online Power App/Sandbox
Paul,
I have a diagnostic process that I go through when I have issues. Confirm all PC Apps & Environments are on the same version. Which I assume they are since you can see other peoples guides.
The piece of information you have not stated is the issue with viewing available Guides in the PC App or on the HL1 or 2?
We have had some issues with seeming them on the HL2 which can expanded the diagnostic tree into permissions for the person (aka author) and device permissions for the Hololens. Which for us those permission can be affected by policies at the company level, department level, or even person level.
In other words, you have to start looking at permission and security roles of the person and Microsoft devices, in this case the hololens. The new Deployment playbook for Dynamics 365 Guides is very nice: https://docs.microsoft.com/en-us/dynamics365/mixed-reality/guides/admin-deployment-playbook for understanding the interplay of these areas.
Understand that sometimes this interplay of roles and security can happen at a higher level when IT does some type of update and perhaps a person permission/security settings get reset to a default state.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (