Page Comparison

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

     Image Added

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

       Image Added

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.

     Image Added

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

   Image Added

9. New environments: Assign a security role to yourself in order to test the application through Advanced Settings.

   Image Added

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

   Remove all connections that are showing as not connected - 5 connections (APSR, MTAPI, SIAPI, SPAPI, TMAPI), Office365Users and APSD_Translations.

   Image Added

4. Add all of them back.

   Image Added

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

   Image Added

6. Check off the APSD_Translations list & click Connect.

   Image Added

7. Run the App Checker and ensure no errors are reported.

   Image Added

8. Turn on “Allow searching” in the properties for the following elements:

   • New Service Request Step One Screen - cboNapaProject element

     Image Added

   • New Service Request Step Three Contact Info Screen - cboFindOrganizationAlt element

     Image Added

   • Service Request Review Screen - ddSRRChangeReAssignment element

     Image Added

   • New Invoice Step One Screen - cboInvoiceCustomer and cboCustomerAddress elements

     Image Added

   • Weekly Time Entry Normalized Screen - cmbProject

     Image Added

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.

   Image Added

8. Upload the csv file from step 4. If there are any mapping issues, fix them.

   Image Added

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.

Name: Timesheet rejected - Send email notification

Description: This Power Automate Flow triggers when the “ap_timesheetstatus” field is modified to “Rejected”. The flow sends an email to the submitter.

Name: Expense rejected - Send email notification

Description: This Power Automate Flow triggers when the “ap_expensestatus” field is modified to “Rejected”. The flow sends an email to the submitter.

Name: Invoice rejected - Send email notification

Description: This Power Automate Flow triggers when the “ap_invoicestatus” field is modified to “Rejected”. The flow sends an email to the submitter.

Name: Flow - Push Approved Time Entries To CRSM

Description: This Power Automate Flow triggers when the “ap_timsheetstatus” field is modified to “Approved”. The flow uses the “TMAPI” custom connector, specifically the following end points: 

1. Add a time entry

   1. To add a time entry, the flow gets all the rows where the current timesheet is approved from the “Time Entries” table filtered via a FetchXML query to only get the rows where “Added to CRSM” is false and hours are not empty or null. Here’s the query:
      

      Code Block
      language xml
      <fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="false">   <entity name="ap_timeentry">     <attribute name="ap_timeentryid" />     <attribute name="ap_timeid" />     <attribute name="createdon" />     <order attribute="ap_timeid" descending="false" />     <filter type="and">       <condition attribute="ap_addedtocrsm" operator="eq" value="0" />       <condition attribute="ap_timesheet" operator="eq" uitype="ap_timesheet" value="{@{triggerOutputs()?['body/ap_timesheetid']}}" />       <condition attribute="ap_employeelogin" operator="eq" value="@{triggerOutputs()?['body/ap_employeelogin']}" />       <condition attribute="ap_timecard" operator="eq" value="@{triggerOutputs()?['body/ap_reportingperiod']}" />       <condition attribute="ap_timeentryhours" operator="not-null" />     </filter>   </entity> </fetch>

   2. Create a time entry record in the CRSM database.
      

      Image Added

2. Add hours to time entry

   1. This endpoint is used to create a record for adding hours for the time entry that was created in the previous step. Depending upon the “ap_timeentrytype” i.e. “Regular”, “Travel” or “Other”, corresponding action is called. 

      

3. At the end of the flow, the flag “Added to CRSM” is set to true in the Time Entries table. 

Push Time Entry to CRSM Step inside flow

TypeCode: Regular (REG), Travel (TH), Other (DH)

[
  {
    "ServiceRequestId": @{int(variables('ServiceRequestID'))},
    "ServiceId": @{outputs('Get_a_row_by_ID')?['body/ap_serviceid']},
  {     "ServiceRequestIdApproverNetworkId": @{int(variables('ServiceRequestID'))triggerOutputs()?['body/ap_approvedby']},
    "ServiceIdComment": @{outputsitems('Get_a_row_by_IDApply_to_each_-_Push_to_CRSM')?['body/ap_serviceidcomments']},
    "ApproverNetworkIdSubmitterNetworkId": @{triggerOutputs(items('Apply_to_each_-_Push_to_CRSM')?['body/ap_approvedbyemployeelogin']},
    "CommentDateTime": @{items('Apply_to_each_-_Push_to_CRSM')?['ap_commentstimeentrydate']},
    "Hours": [
   "SubmitterNetworkId   {
        "Quantity": @{items('Apply_to_each_-_Push_to_CRSM')?['ap_employeelogintimeentryhours']},
    "DateTime    "TypeCode": "REG",
        "IsBillable": @{items('Apply_to_each_-_Push_to_CRSM')?['ap_timeentrydatebillable']},},
        "HoursStatusCode": [2
      {}
    ]
   "Quantity": @{items('Apply_to_each_-_Push_to_CRSM')?['ap_timeentryhours']},
        "TypeCode": "REG",
        "IsBillable": @{items('Apply_to_each_-_Push_to_CRSM')?['ap_billable']},
        "StatusCode": 2
      }
    ]
  }
]

Description: This Power Automate Flow can be manually triggered to import users from an Excel file (see screenshot below) into the Dynamics 365 “Users” table in the target environment. The Flow also associates users with their managers as listed in the Excel file and assigns them the roles as per the Excel file. This Excel file can be stored on the executing user’s OneDrive.  

Image Removed

Image Removed

}
]

Name:Flow – Import Users and Roles

Description: This Power Automate Flow can be manually triggered to import users from an Excel file (see screenshot below) into the Dynamics 365 “Users” table in the target environment. The Flow also associates users with their managers as listed in the Excel file and assigns them the roles as per the Excel file. This Excel file can be stored on the executing user’s OneDrive.  

Image AddedImage Added

There is a bug with D365 that doesn’t allow sharing of custom connectors if they are included in a solution. This means that other developers cannot edit the custom connector.

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

   Image Added

7. Click Share.

   Image Added