10,730
edits
Important: Deprecating old WebView — Publish failed error
Power Automate: Difference between revisions
Jump to navigation
Jump to search
→Sample Power Automate flows
No edit summary |
|||
| Line 23: | Line 23: | ||
=== Questionnaires in Excel table === | === Questionnaires in Excel table === | ||
This flow is triggered when any new Questionnaire is submitted by mobile user in Dataverse. If this questionnaire is not type of template, the body of answered questionnaire | This flow is triggered when any new Questionnaire is submitted by mobile user in Dataverse. If this questionnaire is not type of template, the body of answered questionnaire (initially in the JSON format) is processed and parsed into an Excel table. | ||
;Used connectors: Microsoft Dataverse, Excel Online | ;Used connectors: Microsoft Dataverse, Excel Online | ||
;Business value: | ;Business value: Transfer data harvested via Inspections into XLS for further analytics. | ||
;Prerequisites: Forms + solution/Resco Inspections tables enabled in Dataverse | ;Prerequisites: [[Forms+]] solution/Resco Inspections tables enabled in Dataverse | ||
;Link: [https://docs.resco.net/mediawiki/images/5/52/ParseJSONQuestionnaire.zip Parse JSON Questionnaire] | ;Link: [https://docs.resco.net/mediawiki/images/5/52/ParseJSONQuestionnaire.zip Parse JSON Questionnaire] | ||
=== Questionnaires in Power BI === | === Questionnaires in Power BI === | ||
This flow is triggered when any new Questionnaire is submitted by mobile user in Dataverse. It then refreshes the dataset of Power BI workspace. Dataset refresh is required when | This flow is triggered when any new Questionnaire is submitted by mobile user in Dataverse. It then refreshes the dataset of Power BI workspace. Dataset refresh is required when post-processing of JSON in Power BI because parsing JSON in DirectQuery mode is not available. | ||
;Used connectors: Microsoft Dataverse, Power BI | ;Used connectors: Microsoft Dataverse, Power BI | ||
;Business value: Can be used as help for further analytics of submitted questionnaires in Power BI. | ;Business value: Can be used as help for further analytics of submitted questionnaires in Power BI. | ||
;Prerequisites: Forms + solution/Resco Inspections tables enabled in Dataverse | ;Prerequisites: [[Forms+]] solution/Resco Inspections tables enabled in Dataverse | ||
;Link: [https://docs.resco.net/mediawiki/images/b/b8/RefreshDataSetForPowerBI.zip Refresh Data Set For Power BI] | ;Link: [https://docs.resco.net/mediawiki/images/b/b8/RefreshDataSetForPowerBI.zip Refresh Data Set For Power BI] | ||
=== New reported issue in Guides === | === New reported issue in [[Guides]] === | ||
This flow is triggered when any new Guide Feedback is created by mobile user in Dataverse. If the feedback type is “Guide”, not “Step” and the step ID is not empty, it retrieves a list of system users associated with a specific guide. Then, it sends an email to each user with the comment from the feedback. | This flow is triggered when any new Guide Feedback is created by mobile user in Dataverse. If the feedback type is “Guide”, not “Step” and the step ID is not empty, it retrieves a list of system users associated with a specific guide. Then, it sends an email to each user with the comment from the feedback. | ||
;Used connectors: Microsoft Dataverse, Office 365 Outlook | ;Used connectors: Microsoft Dataverse, Office 365 Outlook | ||
;Business value: Can be used as monitoring/notification tool for guides. | ;Business value: Can be used as monitoring/notification tool for guides. | ||
;Prerequisites: Steps + solution/Resco Guides tables enabled in Dataverse | ;Prerequisites: [[Steps+]] solution/Resco Guides tables enabled in Dataverse | ||
;Link: [https://docs.resco.net/mediawiki/images/d/d0/GuideIssueNotification.zip Guide Issue Notification] | ;Link: [https://docs.resco.net/mediawiki/images/d/d0/GuideIssueNotification.zip Guide Issue Notification] | ||
=== Generate Work Order report === | === Generate Work Order report === | ||
This flow is triggered when a Work Order is selected from list by backend user. It takes this Work Order record and generates new PDF report based on data from Dataverse and Resco report template. After report is generated, it is saved as annotation regarding selected Work Order. | This flow is triggered when a Work Order is selected from a list by a backend user. It takes this Work Order record and generates a new PDF report based on data from Dataverse and Resco report template. After the report is generated, it is saved as an annotation regarding the selected Work Order. | ||
;Used connectors: Microsoft Dataverse, Resco Reports | ;Used connectors: Microsoft Dataverse, Resco Reports | ||
;Business value: Leverage advanced PDF/word reporting of Dataverse records directly in your backend. | ;Business value: Leverage advanced PDF/word reporting of Dataverse records directly in your backend. | ||
;Prerequisites: Existing and enabled Report template for Work Order entity in Resco Report Designer | ;Prerequisites: Existing and enabled Report template for Work Order entity in Resco [[Report Designer]] | ||
;Link: [https://docs.resco.net/mediawiki/images/d/d7/GenerateReportforWorkOrder.zip Generate Report for Work Order] | ;Link: [https://docs.resco.net/mediawiki/images/d/d7/GenerateReportforWorkOrder.zip Generate Report for Work Order] | ||
=== Daily | === Daily summary === | ||
This flow executes every evening and check for new opportunities, work orders and tasks created by every user. If there are any records of these kinds created that day, user gets an email with HTML tables containing summary of newly created records with column or two of information. | This flow executes every evening and check for new opportunities, work orders, and tasks created by every user. If there are any records of these kinds created that day, user gets an email with HTML tables containing a summary of newly created records with column or two of information. | ||
;Used connectors: Microsoft Dataverse, Power Automate Operations, Office 365 Outlook | ;Used connectors: Microsoft Dataverse, Power Automate Operations, Office 365 Outlook | ||
;Business value: Can be used as the end-of-the-day summary notification, either for users or management. | ;Business value: Can be used as the end-of-the-day summary notification, either for users or management. | ||
| Line 63: | Line 63: | ||
=== Sync exception === | === Sync exception === | ||
We check for new records in resco_mobileaudit | We check for new records in the resco_mobileaudit table. If the name of newly created record is "synchronization_finish", we look for exception tags in the text and then parse the exception. Condition checks if there is anything parsed from this record. If yes, we send an email to specific user that gets notification containing the exception and the name of the user that this exception belongs to. | ||
;Used connectors: Microsoft Dataverse, Power Automate Operations, Outlook | ;Used connectors: Microsoft Dataverse, Power Automate Operations, Outlook | ||
;Business value: Can be used as monitoring/notification tool for synchronization. | ;Business value: Can be used as monitoring/notification tool for synchronization. | ||
;Prerequisites: Resco Mobile application with Resco mobile audit enabled | ;Prerequisites: Resco Mobile CRM application with [[Auditing#Mobile_auditing|Resco mobile audit]] enabled | ||
;Link: [https://docs.resco.net/mediawiki/images/6/63/Syncexceptionnotification_20230918111959.zip Sync Exception Notification] | ;Link: [https://docs.resco.net/mediawiki/images/6/63/Syncexceptionnotification_20230918111959.zip Sync Exception Notification] | ||
=== ChatGPT inspection summary === | === ChatGPT inspection summary === | ||
This flow is triggered when a questionnaire record is selected from list by backend user. The PDF report is generated by [[Resco Reports connector]]. The completed questionnaire in the JSON format is then sent as HTTP request to ChatGPT with the prompt to generate overall summary of submitted data. The AI model generates a report summary, which is added to a new email activity regarding the questionnaire’s parent account. The admin, or whoever works with data in the backend, can edit the email body and questionnaire summary from the ChatGPT response. When finalized, the email with the report and summary can be sent directly from Dynamics 365. | This flow is triggered when a questionnaire record is selected from a list by a backend user. The PDF report is generated by [[Resco Reports connector]]. The completed questionnaire in the JSON format is then sent as an HTTP request to ChatGPT with the prompt to generate an overall summary of submitted data. The AI model generates a report summary, which is added to a new email activity regarding the questionnaire’s parent account. The admin, or whoever works with data in the backend, can edit the email body and questionnaire summary from the ChatGPT response. When finalized, the email with the report and summary can be sent directly from Dynamics 365. | ||
;Used connectors: Microsoft Dataverse, Resco Reports, HTTP request, Power Automate Operations | ;Used connectors: Microsoft Dataverse, [[Resco Reports connector]], HTTP request, Power Automate Operations | ||
;Business value: Can be used to generate insights and summaries from complex questionnaire data automatically. | ;Business value: Can be used to generate insights and summaries from complex questionnaire data automatically. | ||
;Prerequisites: Enabled existing Report template for Questionnaire in Report Designer, | ;Prerequisites: Enabled existing Report template for Questionnaire in [[Report Designer]], ChatGPT API key | ||
;Link: [https://docs.resco.net/mediawiki/images/8/80/InspectionsSummary.zip Inspections Summary] | ;Link: [https://docs.resco.net/mediawiki/images/8/80/InspectionsSummary.zip Inspections Summary] | ||
| Line 80: | Line 80: | ||
This flow takes a list of GUIDs of selected account records as input, generates a report using the GUIDs as sources via [[Resco Reports connector]], and saves the report as a PDF file in a SharePoint folder. The file name includes the current timestamp and the original filename from the report headers. | This flow takes a list of GUIDs of selected account records as input, generates a report using the GUIDs as sources via [[Resco Reports connector]], and saves the report as a PDF file in a SharePoint folder. The file name includes the current timestamp and the original filename from the report headers. | ||
;Used connectors: Resco Reports, SharePoint | ;Used connectors: [[Resco Reports connector]], SharePoint | ||
;Business value: Can be used to generate advanced reports/insights from numerous records on backend. | ;Business value: Can be used to generate advanced reports/insights from numerous records on backend. | ||
;Prerequisites: Enabled existing Report template for Account overview in Report Designer | ;Prerequisites: Enabled existing Report template for Account overview in [[Report Designer]] | ||
;Link: [https://docs.resco.net/mediawiki/images/4/4c/GenerateAccountOverviewDocument.zip Generate Account Overview Document] | ;Link: [https://docs.resco.net/mediawiki/images/4/4c/GenerateAccountOverviewDocument.zip Generate Account Overview Document] | ||