Info |
---|
Steps to install APSD in D365 PowerApps platform |
...
Expand |
---|
title | Creating 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.
|
Clone the APSD-PAPS repository to your local computer. On the left hand menu, navigate to Data → Custom Connectors . Click on + New custom connector → Import an OpenAPI file . In the Connector name field, type “APSRNAPA-SNAPA”. Click Import and go to \repos\APSD-PAPS\Custom Connectors\JSON and select the APSRNAPA-SNAPA.json file. Click Continue . Verify that the Host and Base URL point to the correct location for the environment you are in (refer to chart below). For NAPA API only: Set up OAuth security Click Create connector . Click on the Test tab, then + New connection . Enter the API Key (RDIMS 17999814) and click Create connection . 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. For all 5 connectors, share them with the organization.
Click ... → Invite another user → Share with org → Save. Image Removed You can also give edit rights to other developers here. On the left hand menu, navigate to Data → Connections . 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.
|
...
Expand |
---|
title | Update connectors and dropdowns in the Canvas app |
---|
|
* Does not seem to be necessary anymore now that the custom connectors are inside solutions. Edit the APSD-PAPS Canvas app. When prompted, select Don't Allow . Remove all connections that are showing as not connected - 5 connections (APSR, MTAPI, SIAPI, SPAPI, TMAPI), Office365Users and APSD_Translations. Add all of them back. 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 Check off the APSD_Translations list & click Connect . Run the App Checker and ensure no errors are reported. 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
Save and Publish the app.
|
...
Expand |
---|
title | Importing SCRAM task data |
---|
|
Go to the environment that has the master set of data for the SCRAM tasks. Currently, this is QA. On the left menu, go to Data → Tables , then open the Scram Tasks table. On the top menu, click on Data → Export data . Once the export has been successfully completed, click on Download exported data . Unzip the csv file. Switch to the environment you are deploying to. On the left menu, go to Data → Tables , then open the Scram Tasks table. On the top menu, click on Data → > beside Get data → Get data from Excel . Upload the csv file from step 4. If there are any mapping issues, fix them. Click Import . Wait for the process to complete, then verify that the data was imported.
|
Expand |
---|
title | Importing 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.
...