Versions Compared

Version Old Version 44 New Version 45
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.

  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
titleCreating custom connectors in new environment Service Principal Connections

  1. Go to make.powerapps.com.

  2. Click on Flows in the side menu.

  3. Click + New flow > Instant cloud flow.

  4. Select Manually trigger a flow, then Create.

  5. Click + New step > Microsoft Dataverse > select any action.

  6. Click on the … and +Add new connection.

  7. Click Connect with service principal.

  8. Image Added

    The connection name should be “CivAv Service Principal”. The rest of the info is in RDIMS 17999814.

  9. Click Create.

  10. Click on Connections in the side menu (don’t save the flow). You can now see the new connection.

    Image Added
Expand
titleCreating custom connectors in new environment - DEV ONLY
Note

Must be done before importing the solution & only for NEW EMPTY environments.

The custom connectors are now being moved through environments using an unmanaged solution.

The custom connectors cannot be created/added to a solution as there is a bug with Power Apps that does not allow them to be shared in this scenario. The workaround provided by Microsoft also does not work.

  1. Clone the APSD-PAPS repository to your local computer.

  2. On the left hand menu, navigate to Data → Custom Connectors.

  3. Click on + New custom connector → Import an OpenAPI file.

  4. In the Connector name field, type “NAPA-SNAPA”.

  5. Click Import and go to \repos\APSD-PAPS\Custom Connectors\JSON and select the NAPA-SNAPA.json file.

  6. Click Continue.

  7. Verify that the Host and Base URL point to the correct location for the environment you are in (refer to chart below).

  8. For NAPA API only: Set up OAuth security

  9. Click Create connector.

  10. Click on the Test tab, then + New connection.

  11. Enter the API Key (RDIMS 17999814) and click Create connection.

  12. Repeat steps 3-10 to create the rest of the connectors using their json files (SIAPI, SPAPI, MTAPI & TMAPI). *Note: SIAPI doesn’t require an API Key.

  13. On the left hand menu, navigate to Data → Connections.

  14. For each connection, share them with the organization.

    • Click ... → Share → + Add everyone in my org → Save.

    • This must be done so that any changes to the API Key get shared to all users. The update should be instant, if users are not receiving the updated key, they will need to clear their browser’s cache.

...

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 in the side menu, then click Publish all customizations in the top menu bar.

  3. Select the APSD solution.

  4. Click Export → Next.

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

  6. Repeat steps 3-5 with the APSD-PAPS Env Variables, APSD-PAPS Flows and APSD-PAPS Custom Connectors solutions but export them as Unmanaged.

Noteinfo

The Canvas app is inside the APSD-PAPS Flows 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
Info

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

  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_0X.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 both 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 APSD Custom Connectors and APSD Flows solution, if 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.

  1. Edit the APSD-PAPS Canvas app.

  2. When prompted, select Don't Allow.

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

  4. Add all of them back.

  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

  6. Check off the APSD_Translations list & click Connect.

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

  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.

...