Info |
---|
Steps to install APSD in D365 PowerApps platform |
...
Expand |
---|
|
Data will not be migrated between environments through the solution. You will need to perform data migration separately following the steps below. Open the Power Apps Studio and select the environment you are migrating from. Click on Solutions in the side menu, then click Publish all customizations in the top menu bar. Select the APSD solution. Click Export → Next . Increase version number as applicable, and select Managed, then click on Export . Repeat steps 3-5 with the APSD-PAPS Env Variables, APSD-PAPS Flows and APSD-PAPS Custom Connectors solutions but export them as Unmanaged.
Note |
---|
The Canvas app is inside the APSD Custom Connectors-PAPS Flows solution. We have to export them as unmanaged as the host/base path for the custom connectors and flows need to be updated with the appropriate link in the new environment. The Canvas app must also be updated to point to the “new” connectors. |
|
Expand |
---|
|
Info |
---|
Solution Import Order APSD-PAPS Env Variables > APSD-PAPS Custom Connectors > APSD > APSD-PAPS Flows |
Click on Solutions on the left-hand menu and then Import in the top menu bar. Select Browse and point to the zip file, e.g. APSD_PAPS_EnvVariables_1_0_0_X0.zip , created in the export solution steps. "X" will be the current iteration number at the time of deployment. New environments: Click Next twice and create a new connection for both Outlook and Dataverse. 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. Click Import and wait for the process to finish. Import the APSD Custom Connectors and APSD Flows solution, if needed. 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. Even if there are no edits to make, you must still click on Update Connector for it to connect properly.
|
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.
...