Versions Compared

Version Old Version 36 New Version 37
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.

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

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.

* Custom connectors must be created before importing the solution.

Expand
Expand
titleCreating custom connectors in new environment
Note

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

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 → Other → Custom connectorcustom connector → Import an OpenAPI file.

  4. In the Connector Namename field, type “APSR”.

  5. Toggle the Swagger Editor to ON, delete all the code and copy/paste the code from the Click Import and go to \repos\APSD-PAPS\Custom Connectors\JSON and select the APSR.json file.

  6. Toggle the Swagger Editor to OFF.

  7. Ensure you are in the General tab and then verify Click Continue.

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

  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-9 10 to create the rest of the SIAPI connector using the SIAPI.json file.
    **This API connectors using their json files (SIAPI, SPAPI, MTAPI & TMAPI). *Note: SIAPI doesn’t require an API Key.

  13. Repeat steps 3-10 to create the SPAPI connector using the SPAPI.json file.

  14. Repeat steps 3-10 to create the MTAPI connector using the MTAPI.json file.

  15. Repeat steps 3-10 to create the TMAPI connector using the TMAPI.json file.

  16. For all 5 connectors, share them with the organization.

    Click ... → Invite another user → Share with org → Save.

    For all 5 connectors, share them with the organization.

    • Click ... → Invite another user → Share with org → Save.

    • You can also give edit rights to other developers here.

  17. On the left hand menu, navigate to Data -> → Connections.

  18. 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.

...

Migrating the Application Between Environments

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

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 Added

  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 Added

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

    Image Added

  4. Add all of them back.

    Image Added

  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 Added

  6. Check off the APSD_Translations list & click Connect.

    Image Added

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

    Image Added

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

    • New Service Request Step One Screen - cboNapaProject element

      Image Added

    • 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 Added

    • Weekly Time Entry Normalized Screen - cmbProject

      Image Added

  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.

...

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.

...