cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Portal concept

Hi All,

Can someone explain me what is web template, page template and  web page? and when to create what

Every time I create web page should I create web template for that?

Also, Anonymous and authenticated users.

1 ACCEPTED SOLUTION

Accepted Solutions
OliverRodrigues
Super User
Super User

Hi, a few definitions that might help you:

 

  • Web Page - corresponds to a page in your Portal, think as any web page (html) from a web site source code, each page will have the "partial url" which corresponds to the URL of your page, for example /profile
    • in the web page you can define a Web Form/Entity Form/Entity List to be rendered
    • we always have (at least) 2 Web Pages for each page you create in the Portal, one being the root representing the structure of your web page, and the seconds being the content of your web page - to add JS/HTML or anything on the web page you should make changes to the content web page
  • Page Template - defines how your Web Page should be rendered, usually two types:
    • Rewrite - legacy, this points to an .aspx page in the Portals source code, you can't create your own .aspx page, but you can point to an existing one
    • Web Template - this would be the most common, basically this would mean your Web Page will be rendered by a Liquid code and not (directly) an .aspx code
  • Web Template - this will contain HTML/Liquid code (even JS), and contains the code on how your page is being rendered

You don't need to create Page Template/Web Template for every page you are creating, I normally like to use the OOB Full Page, and that already takes care of your page in case you associated an Entity List/Form etc

 

About the roles - the authenticated and anonymous web roles are OOB roles and you don't need to associate those to any contact

by default once signed in to a Portal, that user has the Authenticated Web Role, there is nothing you need to do

 

You can use the roles in many ways, entity permissions, web page access control, etc

 

The official documentation contains lots of definition. There is also a lot of content on YouTube and other platforms on Portals.

I will leave a few links here:

https://365.training/Courses/Detail/Fall_PowerAppsPortals

https://www.youtube.com/c/Powerthon/search?query=portals

https://docs.microsoft.com/en-us/powerapps/maker/portals/

 




If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

Power Pages Super User | MVP


Oliver Rodrigues


 

View solution in original post

1 REPLY 1
OliverRodrigues
Super User
Super User

Hi, a few definitions that might help you:

 

  • Web Page - corresponds to a page in your Portal, think as any web page (html) from a web site source code, each page will have the "partial url" which corresponds to the URL of your page, for example /profile
    • in the web page you can define a Web Form/Entity Form/Entity List to be rendered
    • we always have (at least) 2 Web Pages for each page you create in the Portal, one being the root representing the structure of your web page, and the seconds being the content of your web page - to add JS/HTML or anything on the web page you should make changes to the content web page
  • Page Template - defines how your Web Page should be rendered, usually two types:
    • Rewrite - legacy, this points to an .aspx page in the Portals source code, you can't create your own .aspx page, but you can point to an existing one
    • Web Template - this would be the most common, basically this would mean your Web Page will be rendered by a Liquid code and not (directly) an .aspx code
  • Web Template - this will contain HTML/Liquid code (even JS), and contains the code on how your page is being rendered

You don't need to create Page Template/Web Template for every page you are creating, I normally like to use the OOB Full Page, and that already takes care of your page in case you associated an Entity List/Form etc

 

About the roles - the authenticated and anonymous web roles are OOB roles and you don't need to associate those to any contact

by default once signed in to a Portal, that user has the Authenticated Web Role, there is nothing you need to do

 

You can use the roles in many ways, entity permissions, web page access control, etc

 

The official documentation contains lots of definition. There is also a lot of content on YouTube and other platforms on Portals.

I will leave a few links here:

https://365.training/Courses/Detail/Fall_PowerAppsPortals

https://www.youtube.com/c/Powerthon/search?query=portals

https://docs.microsoft.com/en-us/powerapps/maker/portals/

 




If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

Power Pages Super User | MVP


Oliver Rodrigues


 

Helpful resources

Announcements
Carousel Community Blog

Check out the Community Blog

Read all about the most recent blogs in the community!

Community Call Conversations

Introducing the Community Calls Conversations

A great place where you can stay up to date with community calls and interact with the speakers.

Carousel News & Announcements

What's New in the Community?

Check out the latest News & Events in the community!

Users online (5,307)