Versions Compared

Version Old Version 37 New Version 38
Changes made by

Le, Michelle

Le, Michelle

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

Steps to install APSD in D365 PowerApps platform

...

Expand
titleAdd CivAv application from Azure Portal as an Application User

This must be done in order for the pipeline & for the flows to work (we are using Service Principal account to connect to Dataverse).

  1. Go to the Power Platform admin center.

  2. Select the new environment.

  3. In the Access section, click on See All under S2S Apps.

    Image RemovedImage Added

  4. Click + New app user.

  5. Click + Add an app and enter in the App ID in the search bar.
    CivAv: 22897920-2e0b-4e97-80ca-fbc41c5805cb

  6. Select the business unit for the environment and add System Customizer as a security role.

  7. Click Create.

...

Expand
titleExport the solution

Data will not be migrated between environments through the solution. You will need to perform data migration separately following the steps below.

  1. Open the Power Apps Studio and select the environment you are migrating from.

  2. Click on Solutions on in the left-hand side menu and , then click on the APSD solution.Click Publish all customizations in the top menu bar.Switch to the Overview tab on the side and

  3. click Select the APSD solution.

  4. Click Export → Next.

  5. Increase version number as applicable, and select Unmanaged Managed, then click on Export.

Note

We have to export it as unmanaged due to the custom connectors, which cannot be exported as part of the solution. They need to be recreated in the new environment and then the app must be updated to point to the “new” connectors. Once Microsoft fixes this bug, we can then migrate the connectors as part of the solution and this should allow us to use a managed solution.

Expand
titleImport the solution

  1. Click on Solutions on the left-hand menu and then Import in the top menu bar.

  2. Select Browse and point to the zip file, APSD_1_0_0_X.zip, created in the export solution steps. "X" will be the current iteration number at the time of deployment.

  3. Click Next twice and create a new connection for both Outlook and Dataverse.

    Image Removed

  4. For both connectors, select a predefined system account that is a System Administrator. This information needs to be handed over by the Exchange group, in the DEV environment we are using our own accounts.

  5. Click Import and wait for the process to finish.

  6. Click on Publish all customizations.

Expand
titleUpdate connectors and dropdowns in the Canvas app

  1. Go to edit the Service Request Canvas app.

  2. When prompted, select Don't Allow.

  3. Image Removed

    Remove all connections that are showing as not connected - 5 connections (APSR, MTAPI, SIAPI, SPAPI, TMAPI), Office365Users and APSD_Translations.

    Image Removed

  4. Add all of them back.

    Image Removed

  5. For APSD_Translation, connect to SharePoint data connector. In the box enter the following URL: https://034gc.sharepoint.com/sites/DSD-CivilAviation/Lists/APSD_Translations/AllItems.aspx

    Image Removed

  6. Check off the APSD_Translations list & click Connect.

    Image Removed

  7. Run the App Checker and ensure no errors are reported.

    Image Removed

  8. Turn on “Allow searching” in the properties for the following elements:

    • New Service Request Step One Screen - cboNapaProject element

      Image Removed

    • New Service Request Step Three Contact Info Screen - cboFindOrganizationAlt element

      Image Removed

    • Service Request Review Screen - ddSRRChangeReAssignment element

      Image Removed

    • New Invoice Step One Screen - cboInvoiceCustomer and cboCustomerAddress elements

      Image Removed

    • Weekly Time Entry Normalized Screen - cmbProject

      Image Removed

  9. Save and Publish the app.

Export the solution

Data will not be migrated between environments through the solution. You will need to perform data migration separately following the steps below.

  1. Open the Power Apps Studio and select the environment you are migrating from.

  2. Click on Solutions on the left-hand menu and then click on the APSD solution.

  3. Click Publish all customizations in the top menu bar.

  4. Switch to the Overview tab on the side and click Export → Next.

  5. Increase version number as applicable, and select Unmanaged, then click on Export.

Note

We have to export it as unmanaged due to the custom connectors, which cannot be exported as part of the solution. They need to be recreated in the new environment and then the app must be updated to point to the “new” connectors. Once Microsoft fixes this bug, we can then migrate the connectors as part of the solution and this should allow us to use a managed solution.

  1. Repeat steps 3-5 with the APSD Flows and APSD Custom Connectors solutions but export them as Unmanaged.

Note

The Canvas app is inside the APSD Custom Connectors solution.

We have to export them as unmanaged as the host/base path for the custom connectors and flows need to be updated with the appropriate link in the new environment. The Canvas app must also be updated to point to the “new” connectors.

Expand
titleImport the solution

  1. Click on Solutions on the left-hand menu and then Import in the top menu bar.

  2. Select Browse and point to the zip file, APSD_1_0_0_X.zip, created in the export solution steps. "X" will be the current iteration number at the time of deployment.

  3. New environments: Click Next twice and create a new connection for both Outlook and Dataverse.

    Image Modified

  4. For both connectors, select a predefined system account that is a System Administrator. This information needs to be handed over by the Exchange group, in the DEV environment we are using our own accounts.

  5. Click Import and wait for the process to finish.

  6. Import the APSD Custom Connectors and APSD Flows solution, if needed.

  7. Click on Publish all customizations.

Expand
titleUpdate connectors and dropdowns in the Canvas app

...

  1. Edit the APSD-PAPS Canvas app.

  2. When prompted, select Don't Allow.

...

  1. Image Added

    Remove all connections that are showing as not connected - 5 connections (APSR, MTAPI, SIAPI, SPAPI, TMAPI), Office365Users and APSD_Translations.

    Image Modified

  2. Add all of them back.

...

  1. Image Added

  2. For APSD_Translation, connect to SharePoint data connector. In the box enter the following URL: https://034gc.sharepoint.com/sites/DSD-CivilAviation/Lists/APSD_Translations/AllItems.aspx

...

  1. Image Added

  2. Check off the APSD_Translations list & click Connect.

    Image Modified

  3. Run the App Checker and ensure no errors are reported.

...

  1. Image Added

  2. Turn on “Allow searching” in the properties for the following elements:

    • New Service Request Step One Screen - cboNapaProject element

      Image Modified

    • New Service Request Step Three Contact Info Screen - cboFindOrganizationAlt element

...

    • Image Added

    • Service Request Review Screen - ddSRRChangeReAssignment element

...

    • Image Added

    • New Invoice Step One Screen - cboInvoiceCustomer and cboCustomerAddress elements

      Image Modified

    • Weekly Time Entry Normalized Screen - cmbProject

      Image Modified

...

  1. Save and Publish the app.

Importing/Migrating Data

When setting up a new environment, all lookup data must be brought into the environment. This can be done either through creating a dataflow to migrate data between environments or by importing the data from an Excel spreadsheet.

Expand
titleImporting SCRAM task data
Info

Alternative solution: Follow https://docs.microsoft.com/en-us/powerapps/developer/data-platform/dataverse-odata-dataflows-migration to create a dataflow to migrate the data between environments. This currently exists for QA → ACC.

  1. Go to the environment that has the master set of data for the SCRAM tasks. Currently, this is QA.

  2. On the left menu, go to Data → Tables, then open the Scram Tasks table.

  3. On the top menu, click on Data → Export data. Once the export has been successfully completed, click on Download exported data.

  4. Unzip the csv file.

  5. Switch to the environment you are deploying to.

  6. On the left menu, go to Data → Tables, then open the Scram Tasks table.

  7. On the top menu, click on Data → > beside Get data → Get data from Excel.

  8. Upload the csv file from step 4. If there are any mapping issues, fix them.

  9. Click Import. Wait for the process to complete, then verify that the data was imported.

Expand
titleImporting AP task data 

Follow the same steps for Importing SCRAM task data using the AP Task table instead.

Flows

The service principal account should be used for all connections to the DataVerse.

...