Dynamic Content fields missing from list

[Ben_Love]

I am receiving a Request into Flow, passing this through Parse JSON, and all appears to be working well so far. However when I now add  my next action, there are numerous Dynamic Content fields not appearing in the list of available Dynamic Content. These items WERE there previously, and infact I have a test Action (post to Slack) still in place using these missing fields successfully. 

Why are these fields not appearing in the Dynamic Content list?

[v-micsh-msft]

Hi @Ben_Love,

Well, currently there is no document here to explain that. From my experience, this should be related with the Input data format.

It seems Microsoft Flow would take use of the Data Input format to filter the Dynamic content, then show the available Content in the Popup Window.

You should be able to find the missing content by using the Search at the top of the Dynamic Content Window.

Regards,

Michael

[Ben_Love]

Hi Michael,

Unfortunatley not. Doesn't matter if I search within the Dynamic Content popup window, the fields simply are not there. Is there a way I can code the fields in, rather than relying on the GUI? 

Ben

[v-micsh-msft · Accepted solution]

Hi @Ben_Love,

Yes, there is a way to 'code' the value.

We need the Compose Action and the Workflow Definition Language to make it work.

You may first take a look at the following blog to get a start on this:

Using the Azure Logic Apps Workflow Definition Language (WDL) in Microsoft Flow

Post back if you need any further assistance.

Regards,

Michael

[AlexN]

I'm having more or less the same problem (missing dynamic content fields) for a large JSON structure. (and yes, the workaround can be used, but come on, this is not really how it is supposed to work right?)

When using my JSON I'm also facing another problem:

If 2 subobjects have the same keys, I can't tell which field is which.

Example:

{
    "type": "array",
    "items": {
        "type": "object",
        "properties": {            
            "Object A": {
                "type": "object",
                "properties": {
                    "Id": {
                        "type": "number"
                    }
                }
            },
            "Object B": {
                "type": "object",
                "properties": {
                    "Id": {
                        "type": "number"
                    }
                }
            }
        }
    }
}

The "Id" fields of "Object A" and "Object B" are both shown as "Id". The only way to tell which is which is to use one of the fields, save the flow, close it and then start to edit it again.

Now the fields are shown as "Object A.Id" and "Object B.Id" (but only in the actions, triggers, etc. they are used in. The dynamic content fields in the list are still broken)

[ClaireAllen]

Hi,

I have the same issue, I have just managed to create a flow using a list in SharePoint, when I went to create another flow for a list very similar to the one I have just created, when I start to populate the fields it shows that the Dynamice Contents are missing.

I've even tried to copy the flow and input new connection, still did not work, 

Very frustrating as it worked less than an hour ago and now it does not.

Can anyone help?, I can see below you have an option to code, but unfortunately I do not know code.

Any help / suggestions would be great 

Thank you

[pieronegri]

my 2 cents (and that's not how it should work!)

-given the super simple Json

{

"type": "object",

"properties": {"item": {"type": ["string","null" ] }

}

}

I do 

Compose ->expression->if( contains(string(triggerBody()),'item'), triggerBody()['item'], 'default' )

so if in the body I find the 'item' I use it otherwise 'default'

[Anonymous]

I would like to select an UNLIKE button for the work around.  If MS can come up with a workaround, they certainly can fix this so show the fields you CAN dynamically select.  Not everyone is a programmer....Frustrating this issue has been around this long and its still not on the "fix" radar.

[jbenetti]

How many Microsoft engineers does it take to change a light bulb?

NONE

They simply declare darkness a standard.

😞     shameful these bugs exist in a billion dollar project. "Works as designed"

[SteveTGC]

Try removing the reference to null in the field type definition.

e.g. "type": [ "string", "null" ] -> "type": "string"

and the field appears.

After configuring replace the "type": [ "string", "null" ] 

[gspot]

I just faced the same behaviour as several previous posts describe. I used fields of a parsed JSON directly via "dynamic content" just 2 hours ago, now they're gone. It's unbelievable and frustrating that this bug has been exsting for more than 3 years. Is there any REAL solution so far?