Page Comparison

Data will not be migrated between environments through the solution. You will need to perform data migration separately following the steps below.

1. Open the Power Apps Studio and select the ap-dev-tcd365 environment.

2. Select the solution you need to migrate.

3. Click Export → Publish → Next.

4. Increase the version number as needed (revision # is automatically increased).

5. Select corresponding export as type, then click on Export.

   • Managed: APSD, APSD-PAPS Admin, DataVerse-Security Role

   • Unmanaged: APSD-PAPS Flows, APSD-PAPS Custom Connectors, APSD-PAPS Env Variables

6. Download the exported file.

7. Repeat steps 2-6 for any other solutions required.

1. Go to the desired environment.

2. Click on Solutions on the left-hand menu and then Import in the top menu bar.

3. Select Browse and point to the zip file, e.g. APSD_PAPS_EnvVariables_1_0_0_X.zip, created in the export solution steps.

4. Click Import and wait for the process to finish.

5. Import the rest of the solutions as needed.

6. Click on Publish all customizations.

7. Verify that all the required flows are turned on (flows are inside Flows and Admin solutions).

If any of the flows are off:

1. Select the flow and click Turn on.

2. If there is an error, select the flow and click Edit.

3. If you are brough to a screen asking to confirm the flow connections, ensure all are using the connection references inside the solution then click Continue.

   Image Removed

4. Once you are brought to the flow screen, click Save.

5. Steps 6 - 9 are only for certain flows (e.g. those with a manual trigger).

6. Go back to the solution and click on the flow name to view its details.

7. Click on Edit in the Run only users section.

   Image Removed

8. Ensure that all the connections are using the generic account connections and NOT “Provided by run only user”.

   Image Removed

9. Click Save.

10. Click Turn on.

11. Repeat steps 1-10 for any other flows that are not on.

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 Removed

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

   Image Removed

9. Click Import. Wait for the process to complete, then verify that the data was imported.

Follow the same steps using the AP Task table instead.

1. Open the details screen of the flow you wish to copy.

2. Click the Save As button.

3. Give it a new name, and click Save.

4. Go to your My Flows section, and the new flow should be there in a disabled state.​

5. Go into the details page, and click Edit.

6. Delete the Manually Trigger a Flow trigger.

   • Note: This will delete any variables which this trigger contained

7. ​Select the Power Virtual Agents > When Power Virtual Agents calls a flow trigger.

   • We use this as it requires no inputs to be defined.

8. ​Save the flow.

9. Go back to the Solutions section and select the solution into which you want to import the copied flow.

10. Click Add Existing > Flow > Outside Solutions.

11. Select your flow and click Add.​

12. Edit the flow and swap out the trigger with the Manually Trigger a Flow trigger.

13. Fix any trigger variables which were wiped out during the copy operation.

https://powerusers.microsoft.com/t5/General-Power-Automate/Add-existing-flows-to-Solutions/td-p/258103/page/2

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

[
  {
    "ServiceRequestId": @{int(variables('ServiceRequestID'))},
    "ServiceId": @{outputs('Get_a_row_by_ID')?['body/ap_serviceid']},
    "ApproverNetworkId": @{triggerOutputs()?['body/ap_approvedby']},
    "Comment": @{items('Apply_to_each_-_Push_to_CRSM')?['ap_comments']},
    "SubmitterNetworkId": @{items('Apply_to_each_-_Push_to_CRSM')?['ap_employeelogin']},
    "DateTime": @{items('Apply_to_each_-_Push_to_CRSM')?['ap_timeentrydate']},
    "Hours": [
      {
        "Quantity": @{items('Apply_to_each_-_Push_to_CRSM')?['ap_timeentryhours']},
        "TypeCode": "REG",
        "IsBillable": @{items('Apply_to_each_-_Push_to_CRSM')?['ap_billable']},
        "StatusCode": 2
      }
    ]
  }
]