Page Comparison

Steps to install APSD in D365 PowerApps platform

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.

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

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

* Does not seem to be necessary anymore now that the custom connectors are inside solutions. May still need to be done for the other built-in data connections (SharePoint, Office365) on first import.

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.