Why are only some properties visible in Dynamic Content?

[CrispinF]

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 

triggerBody()?['CreatedByCsUserName']  (which works fine, so there cannot be any absolute reason why I cannot see the properties in the Dynamic Content panel. It feels buggy, but maybe there is some logic here??

[Pstork1]

There are two potential reasons.

1. In Dyamic Content for each action there is often a See more link in the upper right corner of the section for that action.  Click that will expand the available values.  Some are filtered out because they are used infrequently and not showing them by default saves space
2. Dynamic content won't show you values that don't match the data type you need for the item you are filling in.  For example if you initialize an array variable it won't show you standard text fields since you can't use them there anyway.

[CrispinF]

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?

[Pstork1]

Can you post a screenshot of your Flow?  Without more context its hard to say what is going on.

[CrispinF]

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"
            ]
        }
    }
}

and I can access all these properties using triggerBody...

Here's the Translator step showing the Dynamic properties available:

An odd subset of properties visible, same every time.  (I made the translator work on the Description by adding it with triggerBody in the expression builder.)

[CrispinF]

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!  

[Pstork1]

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.