Dynamics 365 CommunityForums Microsoft Dynamics CRM (Archived) Dynamics 365 Customer ...

Dynamics 365 Customer Portal:Web Page isssue

(0) Share

Report

Posted on by Community Member Microsoft Employee

Hi,

We are implementing dynamics 365 portal for a client. When a web page record is created , system creates two records(with same configuration like page template,entity list etc) in the backend for the respective web page .

If we update the page template attribute on the web page record, the changes are not reflected .

As per the screenshot attached,the second record is not updated with the new value i.e Full Page.

Is it a known issue ? Do we need to update this records manually every time for every change in a web page record?

*This post is locked for comments

All responses (2)

Answers (1)

Community Member Microsoft Employee on at

Like (0)

Report

RE: Dynamics 365 Customer Portal:Web Page isssue

Thanks Nicholas
Verified answer

Nicholas Hayduk 2,863 on at

Like (1)

Report

RE: Dynamics 365 Customer Portal:Web Page isssue

Yes, this is a known issue.

The multiple records are there to support multi-lingual. You will always have n+1 records for each page, where n is the number of languages you have configured. There is what's known as the "root" page, as well as one page per language. When you look at the standard "Active Web Pages" view, you're only seeing the root pages; then, when you open one up, you'll see a "Localized Content" subgrid, showing a record for each language. In your case, it sounds like you have one language setup.

The portal will actually use the page template specified on the "Localized" page (not the root page). So while the Page Template on the root page is used to initially create the localized pages, after that it doesn't hold much purpose. Even if you change the Page Template via the front-side editing, it won't set the Page Template on the root page.

It would be possible to create workflows to cascade that change down to the localized pages. If you know you'll only ever have one language, just write a workflow that fires on the change of a page template, and when that happens, update the root page as well. You'd have to make sure you make the changes on the localized page, not the root page for this to work. Otherwise, if you want to make the change to the root page, you'd need a custom workflow activity to iterate over the list of all the localized pages to update the Page Template.

Hope that helps.