Versions Compared

Version Old Version 52 New Version 53
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

...

When setting up a brand new environment, there are a few additional steps that must be done other than simply importing the solution. The custom connectors must be created (as there is currently a bug that doesn’t allow them to be migrated with the solution) and all lookup data must be imported.

* DEV Only: Custom connectors must be created before importing the APSD & Flows solutions.

the solution) and all lookup data must be imported.

* DEV Only: Custom connectors must be created before importing the APSD & Flows solutions.

Expand
titleSet Up in Azure Portal

App Registration

Required for pipelines and as a service principal account in APSD (Dataverse connection). A different client secret is used for each environment.

Image AddedImage AddedImage Added

APSD-PAPS-USERS Group

Used as a security group for the Canvas app as well as for the SharePoint translation list.

Image Added

Key vault

Used for NAPA-SNAPA API secrets and MTOA JWT token. It uses the TC-DevTest-CivAv-RGP.

Image Added
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.

  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
titleImport the solution
Info

Solution Import Order Must be followed or else will break dependencies
APSD-PAPS Env Variables > APSD-PAPS Custom Connectors > APSD > APSD-PAPS Flows

Env Variables & Custom Connectors solutions only have to be imported if there are changes.

  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, e.g. APSD_PAPS_EnvVariables_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: Make sure the CivAv Service Principal Dataverse connection has been created (see steps above). Click Next twice and create a new connection for Outlook and select the CivAv Service Principal connection for Dataverse.

  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 rest of the solutions as needed.

  7. Click on Publish all customizations.

If importing the APSD Custom Connectors solution:

  • Edit the URL of each custom connector to point to the right environment. No longer required

  • Even if there are no edits to make, you must still click on Update Connector for it to connect properly.

Expand
titleUpdate connectors and dropdowns in the Canvas app - NO LONGER REQUIRED

* Does not seem to be necessary anymore now that the custom connectors are inside solutions. May still need to be done for the other built-in data connections (SharePoint, Office365) on first import.

  1. Edit the APSD-PAPS Canvas app.

  2. When prompted, select Don't Allow.

  3. Image RemovedImage Added

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

    Image RemovedImage Added

  4. Add all of them back.

    Image RemovedImage Added

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

    Image RemovedImage Added

  6. Check off the APSD_Translations list & click Connect.

    Image RemovedImage Added

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

    Image RemovedImage Added

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

    • New Service Request Step One Screen - cboNapaProject element

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

    • Service Request Review Screen - ddSRRChangeReAssignment element

    • New Invoice Step One Screen - cboInvoiceCustomer and cboCustomerAddress elements

    • Weekly Time Entry Normalized Screen - cmbProject

  9. Save and Publish the app.

...

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.

...