Versions Compared

Version Old Version 69 New Version 70
Changes made by

Le, Michelle

Le, Michelle

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Steps to install APSD in D365 PowerApps platform
Info
Expand
titleHow to switch to classic D365

Click Solutions → APSD → ... → Switch to classic

...

Expand
titleSecurity roles

If a new security role needs to be created, open an existing role and select Copy Role.

Info

Below are the steps to install APSD-PAPS in D365 PowerApps platform

Setting Up a New Environment

...

Expand
titleCreating Connections for Do Not Reply APSD / Ne Pas Répondre PAPS

  1. Go to https://myaccount.microsoft.com/, click on your profile icon in the top right corner and select Sign in with a different account.

    Image RemovedImage Added

  2. Click + Use another account.

  3. Log in to DoNotReplyAPSD-NePasRepondrePAPS@tc.gc.ca (info in RDIMS 17999814).

  4. In the same browser, go to Power Apps Studio and login as your own account.

  5. Click on Data > Connections in the side menu.

  6. Click on + New connection and select Office 365 Outlook.

  7. Click Create and select the Do Not Reply APSD account that you signed into in Step 3.

  8. Repeat Steps 6-7 for the Office 365 Groups and Excel Online (Business) connections.

You should now have the following connections set up

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.

    • Give edit access to TC-CivAv Azure group.

...

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.

    • Most updates to the app will only require the APSD and Flows solutions to be migrated.

Info

The Canvas apps are inside the APSD-PAPS Flows solution.

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 APSD Service Principal Dataverse connection has been created (see steps above). Click Next twice then select the CivAv APSD Service Principal connection for Dataverse and the shared connections for the APIs. Currently we are using a personal account for the other Microsoft connections however once the generic account is set up, we will be using that.

  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.

  8. New environments: Share the APSD-PAPS Canvas App with Everyone in TC. Uncheck the box at the bottom “Send an email invitation to new users”.

  9. New environments: Assign a security role to yourself in order to test the application through Advanced Settings.

If importing the APSD Custom Connectors solution:
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
Warning

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

  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.

...