I use flows that start with "When a HTTP request is received" and send a bunch of properties for which I define a json schema. But in subsequent steps I find I rarely see all the properties in the Dynamic Content panel, and I cannot find any logic to what I see or do not see at any one time. I keep having to reference properties with the full syntax like
There are two potential reasons.
Thanks for your reply. But it does not explain what I see.
For example, on a Translator step I would expect to see properties that are string data type. But actually I can see three properties, a boolean, a string, and a number. My http JSON schema has several other string properties that are not shown. And I can find no "See more" link.
Any suggestions?
Can you post a screenshot of your Flow? Without more context its hard to say what is going on.
Sure, here's the overview:
Here's the starting schema for the HTTP request:
{ "type": "object", "properties": { "TaskId": { "type": "integer" }, "Description": { "type": [ "string", "null" ] }, "CreatedByUserId": { "type": [ "integer", "null" ] }, "AssignedToUserId": { "type": [ "integer", "null" ] }, "RecordId": { "type": "string" }, "Entity": { "type": [ "string", "null" ] }, "RecordDateTime": { "type": [ "string", "null" ] }, "TargetDate": { "type": [ "string", "null" ] }, "Completed": { "type": "boolean" }, "CompletedDateTime": { "type": [ "string", "null" ] }, "AssignedUserFullName": { "type": [ "string", "null" ] }, "AssignedUserEmail": { "type": [ "string", "null" ] }, "EntitySingularName": { "type": [ "string", "null" ] }, "CreatedByCsUserName": { "type": [ "string", "null" ] }, "CreatedByCsUserEmail": { "type": [ "string", "null" ] } } }
OK I see a pattern now... the accessible properties are not of the correct data type, but they ARE the ones that are not declared as nullable. I guess that maybe makes sense... don't offer up properties that might be null or the flow will fail (maybe?).
But... if I change the schema to make other properties nullable and save the flow and come back in again, they are still not accessible to the Translator. So I'm unsure about this theory after all!
After you made the additional properties non-nullable did you remove and re-add the Translator action? It may be that the action picked up the list of Dynamic content when you added it to the Flow and didn't readjust just becuase you modified the JSON schema. Other than that I don't know. I agree it doesn't make a lot of sense. As you mentioned you can manually override it by typing in the Trigger formula. So I think it probably works this way to try to keep more novice users from adding things that may not work. Probably erring on the side of caution by the developers.
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
User | Count |
---|---|
29 | |
28 | |
24 | |
17 | |
10 |
User | Count |
---|---|
66 | |
58 | |
29 | |
27 | |
25 |