Issue: When navigating to a web page on the portal, the title, copy, or other content present on the web page does not match the expected values, even after confirming that cache invalidation is occurring successfully.


This is likely caused by two or more Web Page records in Dynamics 365 sharing the same "Partial URL" value and the same "Parent Page".  While there is logic that forces the parent home page associated to a Website to use a "Partial URL" value of "/", there is currently no logic to ensure that every "Partial URL" value is unique when it shares the same parent, and therefore two or more Web Page records can be created with the same "Partial URL" value.

For example, portals are deployed with a default "Contact Us" Web Page that uses a "Partial URL" value of "contact-us" and is associated with the root "Home" page. If a new "Notify Us" Web Page is created that features a "Partial URL" value of "contact-us" and uses "Home" as its parent while the previous record is still present and active, only one of these pages will be rendered to portal users when they navigate to https://portalurl/contact-us/.

When Dynamics 365 is queried for the Web Page record that matches the URL path, the record with the most recent creation timestamp will be returned. Therefore, the most recently created Web Page record with the duplicate "Partial URL" value will be the one that is rendered on the portal to users.

Resolution: To fix this, a Dynamics 365 administrator can navigate to Portals -> Web Pages and validate that all active records have a unique "Partial URL" value. If two or more Web Page records contain the same "Partial URL" value, then all but one of the duplicate values should be deactivated, deleted, or changed to an alternate path.






Issue: When unauthenticated / unregistered users navigate to one or more web pages on the portal, they are routed to an "Access Denied" page that requires them to sign in.


The custom Web Page Access Control Rule entity in Dynamics 365 allows portal administrators to control whether a portal user can modify content on a page or if they should instead be restricted from reading it. If one or more web pages cannot be accessed, it is most likely that a Web Page Access Control Rule record is keeping the user(s) from being able to do so.

This can be especially problematic if a Web Page Access Control Rule record is created with the "Restrict Read" right associated to the "Home" web page, and then assigned to a Web Role with the "Anonymous Users Role" value set to "Yes". In this situation, all unregistered users will be unable to access the Home page and all child pages (effectively, the entire website) without first registering for a user account. If user registration has been disabled, then the website is entirely locked down and inaccessible to all but previously registered users or administrators.

Of course, this could also be a deliberate design for security purposes or to ensure that the portal is unavailable until it’s ready for public consumption, such as during the development phase.

Resolution: If a redirect to the "Access Denied" page is unwanted, a Dynamics 365 administrator can navigate to Portals -> Web Page Access Control Rules and validate the configuration of the records contained there. Any records configured for a right of "Restrict Read" should be checked to ensure that they meet the security requirements of the portal website.

Interested in more troubleshooting tips for Dynamics 365 portals? Check out the first installment for an overview of all topics covered throughout this series.