Work with Power Apps portals

Intermediate
App Maker
Functional Consultant
Administrator
Power Platform
Power Apps

Power Apps portals are designed for interaction with the internal and external audiences. There are additional requirements for content management and design, as well as the need to secure the content. This learning path describes how portal components work within context of Dynamics 365 to deliver the content and Microsoft Dataverse data to external and internal audiences. We will cover the topics of user authentication and how to secure access to different parts of the portal content based on the target audience and relationship to the content.

Prerequisites

  • Power Apps trial subscription.
  • Basic understanding how to navigate a model-driven app.

Modules in this learning path

Note

Effective November 2020

  • Common Data Service has been renamed to Microsoft Dataverse. Learn more.

  • Some terminology in Microsoft Dataverse has been updated. For example,entity is now table and field is now column. Learn more.

Modules will be updated soon to reflect the latest terminology.

Portal makers spend the majority of their time configuring portals by using Microsoft Power Apps portals Studio. It is important that portal makers have a full understanding of the capabilities and also the limitations of using portals Studio. This module will focus on understanding and using Power Apps portals Studio to create and customize portal websites. Power Apps portals Studio allows makers to add and configure webpages, layout components, static content, custom CSS files, entity lists, and entity forms.

Note

Effective November 2020

  • Common Data Service has been renamed to Microsoft Dataverse. Learn more.

  • Some terminology in Microsoft Dataverse has been updated. For example,entity is now table and field is now column. Learn more.

Modules will be updated soon to reflect the latest terminology.

Makers are required to understand the various Power Apps portals metadata components so they can configure the portals app for a variety of unique requirements. This module uses the Portal Management app to configure various portals features by editing the portals metadata.

Note

Effective November 2020

  • Common Data Service has been renamed to Microsoft Dataverse. Learn more.

  • Some terminology in Microsoft Dataverse has been updated. For example,entity is now table and field is now column. Learn more.

Modules will be updated soon to reflect the latest terminology.

The ability to find and interact with Dataverse data on a website is one of the core benefits of implementing a Power Apps portal. Several methods are available for you to display Dataverse data. Learning and knowing about these different options will help you have successful portal implementations. This module will focus on the techniques that you can use to configure entity lists, entity forms, and web forms to build powerful web applications.

Note

Effective November 2020

  • Common Data Service has been renamed to Microsoft Dataverse. Learn more.

  • Some terminology in Microsoft Dataverse has been updated. For example,entity is now table and field is now column. Learn more.

Modules will be updated soon to reflect the latest terminology.

Liquid is an open-source template language that is integrated natively into Microsoft Power Apps portals. It acts as a bridge between Dataverse and the HTML or text output that is sent to the browser. Liquid can be used to add dynamic content to pages and to create a variety of custom templates. Additionally, Liquid provides access only to the data and operations that are explicitly allowed by the portals.

Note

Effective November 2020

  • Common Data Service has been renamed to Microsoft Dataverse. Learn more.

  • Some terminology in Microsoft Dataverse has been updated. For example,entity is now table and field is now column. Learn more.

Modules will be updated soon to reflect the latest terminology.

The concept of exposing Dataverse on a public webpage is appealing for addressing numerous business requirements. However, careful consideration is necessary to avoid exposing private or sensitive data. This module will focus on helping you understand and configure portal security to protect static and dynamic content and limit visibility to specific audiences.

Note

Effective November 2020

  • Common Data Service has been renamed to Microsoft Dataverse. Learn more.

  • Some terminology in Microsoft Dataverse has been updated. For example,entity is now table and field is now column. Learn more.

Modules will be updated soon to reflect the latest terminology.

A portal maker should consider specific details when designing and building portals. Implementing a portal solution requires knowledge of the specific business requirements and needs of the customer. Along with being simplistic and well-designed, a successful portal should provide functionality in consideration of geographical location, language, and accessibility needs. Additionally, portal makers should ensure that portal metadata is backed up to source control and deployed to test and production environments in a consistent and structured way.