Versions Compared

Version Old Version 7 New Version 8
Changes made by

Le, Michelle

Le, Michelle

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Return to the modern Power Apps UI and select the environment you are migrating from.

  2. Click on Solutions on the left-hand menu and then click on the APSD solution.

  3. Click Publish all customizations in the top menu bar.

  4. Click Export → Next.

  5. Increase version number as applicable, and select Unmanaged, then click on Export.

Note

We have to export it as unmanaged due to the custom connectors, which cannot be exported as part of the solution. They need to be recreated in the new environment and then the app must be updated to point to the “new” connectors. Once Microsoft fixes this bug, we can then migrate the connectors as part of the solution and this should allow us to use a managed solution.

Creating custom connectors in new environment

...

  1. On the left hand menu, navigate to Data → Custom Connectors

  2. Click on + New → Other → Custom connector.

  3. In the Connector Name field, type “APSR”.

  4. Toggle the Swagger Editor to ON, delete all the code and copy/paste the code from the APSR.json file.

  5. Toggle the Swagger Editor to OFF.

  6. Ensure you are in the General tab and then verify that the Host and Base URL point to the correct location for the environment you are in (refer to chart below).

  7. Click Create connector.

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

  9. Enter the API Key (ask Le, Michelle for them) and click Create connection.

  10. Repeat steps 3-9 to create the SIAPI connector using the SIAPI.json file.
    **This API doesn’t require an API Key.

  11. Repeat steps 3-10 to create the SPAPI connector using the SPAPI.json file.

  12. Repeat steps 3-10 to create the MTAPI connector using the MTAPI.json file.

  13. Repeat steps 3-10 to create the TMAPI connector using the TMAPI.json file.

  14. For all 5 connectors, share them with the organization.

    • Click ... → Invite another user → Share with org → Save.

      Image RemovedImage Added

    • You can also give edit rights to other developers here.

Environment

Host

Base URL

Dev

http://wwwappstestext.tc.gc.ca

http://ncdtmsaapp.azurewebsites.net

/Saf-Sec-Sur/2/NDWL2-LWND2-API
/Corp-Serv-Gen/5/SIAPI-ISAPI-DEV
/Corp-Serv-Gen/5/SPAPI-PSAPI-DEV
/Saf-Sec-Sur/13/MTAPI-INT
/

QA

“

“

Prod

Expand
titleMicrosoft Bug: Cannot share custom connectors contained within a solution (Workaround - FAILED)

There is a bug with D365 that doesn’t allow sharing of custom connectors if they are included in a solution. Workaround: https://youtu.be/ROKO589RBnQ

  1. Go to Data → Tables → Connector table → Data tab.

  2. Select the connector and click on Edit Record.

  3. Click SHARE → Add User/Team → Select Team in the Look for dropdown.

  4. Check off the team that is named after the environment.

  5. Click Select → Add.

  6. Ensure that they only have Read access (for other users, refer to chart below).

  7. Click Share.

    Image RemovedImage Added

Import the solution

  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, APSD_1_0_0_X.zip, created in the export solution steps. "X" will be the current iteration number at the time of deployment.

  3. Click Next twice and create a new connection for both Outlook and 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. Click on Publish all customizations.

Importing SCRAM task data

  1. Import data for Scram Task table from Scram_Task.csv file that is provided.

26.   Select Scram Task table and opt for Get data from Excel

...

  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 search for Scram Tasks.

  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 search for Scram Tasks.

  7. On the top menu, click on Data → > beside Get data → Get data from Excel.

    Image Added

  8. Upload the csv file from step 4.

    Image Added

27.   Select the csv file and click on Map Columns

...