Microsoft released new Power Apps portals in late 2019, joining the Power Apps family of Canvas apps and model-driven apps.

The work of adding the Power Apps portal to the suite was long overdue. While Canvas and model-driven apps make it much easier to develop apps than InfoPath, they can't be used to build public apps for anonymous users. This void has now been filled by the Power Apps portal. What exactly is Power Platform?

In other words, Power Platform is a collection of no-code/low-code tools. Power Apps, which are made up of Power Apps portals, canvas apps, and model-driven apps, are among the tools available on the platform.

Apps for Microsoft Power Platform

Power Platform has tools:

  • Power BI is a program that allows you to create business intelligence dashboards and reports.
  • Power Apps - To create applications that collect custom information.
  • Canvas apps are used to create apps from a blank canvas.
  • Model-driven apps are used to build apps that are based on your data model and business process.
  • Portals are used to create websites that are accessible to external and/or authenticated users. Power Automate - for creating information processing workflows.
  • Power Virtual Agents are used to build chatbots.

What are we learning today?

  • We will learn the following in this blog post:
  • When should the Power Apps portal be used?
  • Architecture for the Power Apps portal.
  • How to create a Power Apps portal for the first time.

When to use Power Apps Portals

The Power Apps portal has two primary applications:

You want to create a public-facing website that anonymous and/or authenticated users can access.

You may want to combine other Microsoft technologies, such as embedding Power BI dashboards and/or reporting into your website, to create a unified experience.

When a user fills out a form on your website, the workflow is triggered. To store documents, use Azure Blob Storage and/or SharePoint.

To keep track of how your solution is being used, use Application Insights.

Architecture of Power Apps Portals

The Power Apps portal is not a new concept at all. It's been around for a while, but it was formerly known as "Dynamics 365 Portals" and was only available as an add-on for Dynamics 365 model-driven apps. Appearance of the solution is governed by the Bootstrap 3.3.x framework as well as the Liquid template language. Common Data Service is the foundation of the Power Apps Portal (CDS). All data on your portal, such as pages, page templates, forms and form data, will be stored in the CDS database.

Important: There can be only one portal in each Power Apps environment. If you need to create a second portal, you will need to create another environment.

Before we start building the portal we will need two things:

An environment for Power Apps

Power Apps environment with CDS database

In the Power Apps portal, create your first portal.

In this tutorial, I will combine my interests in the personal health and power platform. On top of the Power Apps portal, we will create a gym signup form. When you submit the form, the information will be saved in our CDS database. This is how the final product will appear.:

Signup Form in Power Apps Portal

To get there, we'll take the following steps:

Create a CDS database in the new Power Apps environment.

As a CDS entity, create a gym signup form.

Build a portal for Power Apps.

Add the form to the portal.

Create a CDS database in the new Power Apps environment.

You must have at least one Power Apps environment when you can log in to https://make.powerapps.com. If you haven't already, you can use your existing environment to create a new portal. However, if you need to create a new environment, follow these steps: To get started, visit https://make.powerapps.com.

  • Go to the top right corner of the page and click on the gear.
  • Then choose Administration Center.
  • Getting a new Power Apps environment up and running
  • In the left navigation bar, select Environments.
  • In the top navigation bar, select + New.
  • Create a new setting.
  • A new environment form will appear on the screen.

Fill in the blanks:

  • Choose a name for your environment.
  • Type: Experiment Choose your location.
  • Fill in the blanks with the objective of your environment.
  • Is it necessary to create a database for this environment?
  • Next should be selected.
  • A form will appear for adding a database.

Fill in the blanks:

  • Choose your preferred language.
  • Select the currency of your choice.
  • Apps for Dynamics 365 must be enabled: No (this option should be grayed out because we selected "Trial" for the trial period). environment type)
  • No-click deployment of sample apps and data
  • Your environment should be ready in no time.
  • Create a CDS entity for gym signup form.
  • The next step is to create our gym signup form while the Power Apps environment is ready. To begin, we will create a new CDS entity called Gym Membership. After that, we'll add our Lastly, we will add fields to the entity and create the form. The entity can be compared to a database table.

Related Post