Page Comparison

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

Setting up a new environment may take up to an hour.

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 Added

4. Click + New app user.

5. Click + Add an app and enter in the App ID in the search bar.
   CivAv-APSD-PAPS: 27b29278-594f-484d-a0c0-9c61381bad31

   Image Added

6. For the business unit, select the one with the environment name.

7. Edit the security roles and select System Administrator and System Customizer.

8. Click Create.

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

5. Click on 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 Microsoft Dataverse Office 365 Groups and Excel Online (Business) connections.

You should now have the following connections set up

Image Added

1. Open the Power Apps Studio and click on Flows in the side menu.

2. Click + New flow > Instant cloud flow.

3. Select Manually trigger a flow, then Create.

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

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

6. Click Connect with service principal.

7. Image Added

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

8. Click Create.

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

   Image Added

10. Delete any other connections that were created.

1. Open the Power Apps Studio and select the ap-dev-tcd365 environment.

2. Select the solution you need to migrate.

3. Click Export → Publish → Next.

4. Increase the version number as needed (revision # is automatically increased).

5. Ensure they are all exported as Managed, then click on Export.

   • Managed: APSD, APSD-PAPS Admin, DataVerse-Security Role

   • Unmanaged: APSD-PAPS Flows, APSD-PAPS Custom Connectors, APSD-PAPS Env Variables

6. Download the exported file.

7. Repeat steps 2-6 for any other solutions required.

1. Go to the desired environment.

2. Once the Env Variables solution has been imported

   • Edit the variables to ensure they have the correct values for the environment. This must be done through the Default solution.

3. Once the Custom Connectors solution has been imported

   • For the NAPA connector, go to the Security tab and enter in the information as per RDIMS 17999814.

     • Depending on the settings, the NAPA connector may be pointing to prod rather than dev, so make sure to use correct client ID/secret when setting up the connector.  

   • Click Update connector.

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

   • Click X Close.

   • For the rest of the connectors, edit them and go to the Test tab, then click + New connection (API key keys are in RDIMS 17999814 or key vaults (Dev / Prod)).

   • On the left-hand menu, click on Data/Dataverse > Connections.

   • For the MTAPI, SPAPI & TMAPI connections, 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.

       

4. Import the APSD solution

5. When importing the Flows solution

   • Click Next twice then select the CivAv APSD Service Principal connection for Dataverse and the shared connections for the APIs.

   • For the Office 365 and Excel Online connections, select the Do Not Reply APSD / Ne Pas Répondre PAPS connection created earlier.

     

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

7. Click on Publish all customizations.

8. Verify that all the required flows are turned on. If any are off, follow the steps at the end of this section.

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

   

10. Share the Canvas apps with the other developers individually, checking off the co-owner box.

11. PROD ONLY: Edit the APSD-PAPS Canvas App. Go into the App.OnStart() and edit the MTOA JWT token to the Production one.

12. Assign a security role to yourself in order to test the application.

    • Can be done through Advanced Settings or the Admin center (see Granting security roles to users section).

      

If ‘Modify Users’ flow is off, turn on ‘Remove User’ and ‘Update User’ flows first (if not already on).

1. Select the flow and click Turn on.

2. If there is an error, select the flow and click Edit.

3. If you are brough to a screen asking to confirm the flow connections, ensure all are using the connection references inside the solution then click Continue.

   

4. Once you are brought to the flow screen, click Save.

5. Steps 6 - 9 are only for certain flows (e.g. those with a manual trigger).

6. Go back to the solution and click on the flow name to view its details.

7. Click on Edit in the Run only users section.

   

8. Ensure that all the connections are using the generic account connections and NOT “Provided by run only user”.

   

9. Click Save.

10. Click Turn on.

11. Repeat steps 1-10 for any other flows that are not on.