{"id":25319,"date":"2020-10-29T11:18:29","date_gmt":"2020-10-29T11:18:29","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=25319"},"modified":"2020-11-18T07:46:59","modified_gmt":"2020-11-18T07:46:59","slug":"formatting-output-result-for-your-actions-in-custom-connector","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2020\/10\/formatting-output-result-for-your-actions-in-custom-connector\/","title":{"rendered":"Formatting Output result for your actions in Custom Connector"},"content":{"rendered":"

Continuing with the series on Custom Connector<\/a>, today I touch upon output results of your actions. If you have worked with any of the existing connectors including Common Data Service connectors, you will notice that when you choose an action like List or Read, the CRM record object returns individual field values of the record as properties that you can then easily use through the Dynamic Values option further in your flow.<\/p>\n

When creating a custom connector, say we return a JSON object as the result from the Azure function, you will notice that without any formatting, the output will appear as<\/p>\n

\"Formatting<\/a><\/p>\n

The JSON object is available in the body but to read the individual properties from in there, you would need to use the expression in the form of<\/p>\n

outputs(‘GetEmployeeDetail’)?[‘body\/FirstName’]<\/strong><\/p>\n

If the JSON result is of the form<\/p>\n

\"Formatting<\/a><\/p>\n

While it is accessible through expression, it would be user friendly if we could have it available as a property that could be referenced directly as a field when listing dynamic values to choose from.<\/p>\n

For this make sure to define the response format in your custom connector<\/p>\n

\"Formatting<\/a><\/p>\n

Double click on default to open the response editor<\/p>\n

\"Formatting<\/a><\/p>\n

In the import from sample window provide the JSON object of your result, to see it populate the properties automatically<\/p>\n

\"Formatting<\/a><\/p>\n

With this done, now when you look for the dynamic values for your action result, you will find it in the form of<\/p>\n

\"Formatting<\/a><\/p>\n

Consider scenario where your JSON result is in nested JSON format as below.<\/p>\n

\"Formatting<\/a><\/p>\n

In that if any of the field names is same in the entire JSON object irrespective of whether it is in parent or child node, it will appear as duplicate properties as below.<\/p>\n

\"Formatting<\/a><\/p>\n

Be careful with your properties names in the JSON object to avoid this scenario.<\/p>\n

Make sure to set the response properties appropriately for your actions in custom connector<\/a> to make it more user friendly.<\/p>\n","protected":false},"excerpt":{"rendered":"

Continuing with the series on Custom Connector, today I touch upon output results of your actions. If you have worked with any of the existing connectors including Common Data Service connectors, you will notice that when you choose an action like List or Read, the CRM record object returns individual field values of the record\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[2088,16,19,1985],"tags":[2089,545,592,1169,1338,1975],"class_list":["post-25319","post","type-post","status-publish","format-standard","hentry","category-custom-connector","category-dynamics-365","category-dynamics-crm","category-power-automate","tag-custom-connector","tag-dynamics-365-crm","tag-dynamics-crm","tag-microsoft-power-apps","tag-power-apps-dynamics-365-crm","tag-power-automate"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/25319","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=25319"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/25319\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=25319"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=25319"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=25319"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}