In my previous blog post, I talked about the overall page structure for a Dynamics 365 Portals page, and the main elements included in the rendered page, including the Header, Footer, and the Page Content. In this post, I get into the details about where code might be within the Page Content.
So if the code you’re looking for isn’t in the Header or Footer Web Templates (or other Web Templates referenced by them), most likely the code is coming from something more page-specific. One place to look is the Web Template that is references by the Page Template.
The Web Template referenced in the Page Template defines how the Page Content is displayed. It’s possible that the code you’re looking for was included as part of this Web Template (or in a Web Template it includes). It’s also typically the job of this Web Template to include the Copy attribute of the Web Page, which leads me to the more likely locations of the custom code.
It is the responsibility of whomever implements the Web Template used by the Page Template to include the Copy and Summary attributes on a page (typically the Summary field is used on parent pages to show as introductory text along with a link to the child page). If the Page Template doesn’t include it, whatever you put in those fields won’t appear on the page.
Also note that these fields all support Liquid code, so it’s completely possible to use the include Liquid tag to reference other code.
Next, we’ll go further down the rabbit hole and look at Entity Forms, Entity Lists, and a few other places.