I'm wondering if anyone knows of a website where the Microsoft Flow team are publishing known bugs, open issues, priorities and estimated fix dates?
The reason I'm asking is that a lot of our clients are being given access to Microsoft Flow with their Dynamics 365 licenses. They are then asking us to demonstrate how to use Flow with CRM to enhance the product. For example, one client wanted to be able to automate the retrieval of data from CRM each day and storage into an Excel Online file in OneDrive.
Through several attempts to get the CRM connector to work, including the scenario I described above, we have run into lots of problems, mostly cryptic error messages relating to the underlying workflow definition code that we can't access.
For example, when using the "List records" action for Dynamics 365 CRM, we're getting the following error (or similar to it) consistently:
"Unable to process template language expressions in action 'Update_file' inputs at line '1' and column '11': 'The template language expression 'body('List_records')['msft_date']' cannot be evaluated because property 'msft_date' doesn't exist, available properties are '@odata.context, value'. Please see https://aka.ms/logicexpressions for usage details.'."
It turns out that there's an easy fix for this problem. In a Logic App, we created the same action, ran into the same bug and then fixed the workflow definition to resolve the issue. But we can't make that same fix in Flow. And that's what our customers want to use!
Again, my main question is when can we tell our clients that Flow is ok for them to use with CRM? We'd like to see a list of the known problems that the Flow QA team has run into and when a fix is likely to be released.
Thanks for using Microsoft Flow, and apologize for the trouble that you have encountered.
Currently there is no official document available regarding the part you mentioned ( bugs, open issues, priorities and estimated fix dates), in details, there is document available about the release notes:
Which would include the known issues and the corresponding resolution.
You may also take a look at the Flow ideas forum:
This forum would cover the features that users would like Microsoft Flow to have in the future, and the issues under normal usage.
Besides, regarding the error message you shared here, please take a look at the compose action, which could accept the dynamic content as parameter and output the corrseponding results.
Hope the information above is helpful.
Here's how to repro the bug we're running into in case someone wants to look into it...
Test 1: Write CRM data to Excel in OneDrive (FAILED)
1) Create an Excel file. One column named "TimeEntryDate". Name the range (A1) "TimeEntries" and format range as table. Save file.
2) Upload Excel file to OneDrive with name "TimeEntries".
3) Open Flow. Click "Create from blank"
3A) Set trigger to Recurrence. Frequency: Hour Interval: 1
3B) Click "+ New step" then "Add an action". Select "Dynamics 365 - List records"
3C) Select the organization and entity (I chose a custom entity named TimeEntries).
3D) In order to test the work in progress, click "Create Flow" and ran the flow. It worked without error.
3E) Add an "Apply to each" action loop. Select "value" from the previous step (Note: "value" is the name of the collection of data coming from CRM)
3F) Within the "Apply to each" box, select "Add an action". Select "Excel - Insert row". Select file name "/TimeEntries.xlsx".
3G) In the "Insert row" action box, map the Date field (from the TimeEntries CRM entity) to the TimeEntryDate Excel column.
3H) Click "Update Flow". Click Done and then run the Flow. It fails with an error message.
Unable to process template language expressions in action 'Insert_row' inputs at line '1' and column '1954': 'The template language expression 'body('List_records')['altriva_date']' cannot be evaluated because property 'altriva_date' doesn't exist, available properties are '@odata.context, value'. Please see https://aka.ms/logicexpressions for usage details.'.
Revised Test 1: Replace Excel with Compose action (FAILED)
1) Click "Edit Flow". Delete the "Excel - Insert row" action. Save and run the flow again.
2) The flow runs without error, but the "Apply to each" doesn't have any child actions.
3) Add a "Compose" action and select the Date field as the input. Update flow and run it again.
4) Flow fails with the same error message noted above.
It's possible to query data from Dynamics 365 CRM but attempting to invoke an action on the records received leads to an error and the Flow fails.
Apologize for the late response.
Please take a try to search the Value in the dynamic content, then add that under the Compsoe input.
Thne check if there would still be any errors.