Page Comparison

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

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.

   

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/Dataverse > 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

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.

   • Any future deployments will only require the APSD and Flows solutions to be migrated.

   • EXCEPTION: Custom Connectors solution must only be migrated if there are any changes to the existing custom connectors or a new custom connector is added.

   • EXCEPTION: Env Variables solution must only be migrated if new environment variables are added.

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.

   • Only import the exported solutions from the previous section.

3. New environments only, once Custom Connectors solution is imported:

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

   • Go into the APSD-PAPS Custom Connector solution.

   • Click on + New > Automation > Custom connector

     

   • Enter in the info as follows:

     • Connector Name: NAPA-SNAPA

     • Host: www

   • Click Create connector

   • On the left-hand menu, click on Data/Dataverse > Custom connectors

   • Beside the NAPA-SNAPA connector, click ... > Update from OpenAPI file.

     Image RemovedImage Added

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

   • Click Continue.

   • Toggle the Swagger Editor ON > OFF.

   • Go to the Security tab and enter in the information as per RDIMS 17999814.

   • 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 are in RDIMS 17999814).

   • 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. New environments (when importing the Flows solution):

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

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

     

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.

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.

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.

Follow the same steps for Importing SCRAM task data using the AP Task table instead.