Exercise – Create a new solution

  • 4 minutes

In this exercise, you'll create a new solution in the Power Apps maker portal and add the relevant Dataverse objects. This solution provides you with the workspace and objects needed to create a new model-driven app with virtual health data tables.

Prerequisites

To complete the steps in this exercise, you need to meet the following prerequisites:

Create the publisher

In this task, you'll create your own publisher, which helps you uniquely identify your application and new components that you create.

  1. Go to Power Apps.

  2. Select the environment.

    Screenshot of the environment selected.

  3. Select Solutions on the left navigation pane and then select + New solution.

    Screenshot of New solution selected from the ribbon.

  4. Select New publisher and then enter the publisher details as follows:

    • Display name - Virtual Health Data Tables

    • Name - VirtualHealthDataTables

    • Description - Sample application using Virtual Health Data Tables

    • Prefix - vhdt

    Screenshot of the New publisher dialog with details filled in.

  5. Select Save.

Create the solution

The solution provides you with a collection of the components that you use when creating your new model-driven application. The solution also provides a method for versioning and deployment between environments.

  1. In the New solution panel, select the New solution and then enter details as follows:

    • Display name - Virtual Health Data Tables

    • Name - VirtualHealthDataTables

    • Publisher - Virtual Health Data Tables(VirtualHealthDataTables)

    Screenshot of the details for the newly created solution.

  2. Select Create.

Add tables to the solution

In this task, you'll add tables to the solution that you can use and update as part of the application.

  1. From the upper toolbar, select Add existing and then select Table.

    Screenshot of the Add existing menu and Table selected.

  2. In the Add existing tables panel, search for and select the Contact table. Select Next.

    Screenshot of the Contact table selected in the Add existing tables panel.

  3. In the Selected tables panel, select Include all objects. This step selects Include table metadata and turns off the option.

    Screenshot of the Include all objects checkbox selected.

  4. Select Add to complete the step.

  5. Select Add existing and then select Table.

  6. In the Add existing tables panel, search for the msemr_ve_encounter table. Select all available tables and then select Next.

    Screenshot of all tables selected.

  7. In the Selected tables panel, select Include all objects for all tables in the list.

  8. Select Add.

  9. Repeat the previous steps for the following search values:

    • msemr_ve_observation

    • msemr_ve_allergy

    • msemr_ve_episode

The solution should contain the Contact table, which represents the patient in the system. Additionally, it should contain several virtual tables that represent data that's related to the patient, all aligning to corresponding FHIR resources.

Virtualized tables that you use in virtual health data tables mirror their standard table counterparts. Also, the logical names follow a naming convention of including _ve_ as part of the prefix. For example, the virtual version of Encounter has the logical name of msemr_encounter, while the virtual version is named msemr_ve_encounter. Each related expansion table follows the same naming convention.

Now that the tables are added to the solution, you can start to build the model-driven app.