About the button trigger bug, what caused the manual trigger to be NULL

[MoonForYoung]

When this bug occurred to me, I searched the community with little info to help me solve this problem.

The Pop-out shows the error message: The Input body dor trigger 'manual' of type 'Request' did not math its schema defination. Error details:'Invalid types. Expected String but got Null'.

So I did some tests to help me clarify what caused the conflict. according to the message, I think with a high possibility that the ’manual’ trigger should be the chief culprit. therefore I simplified the process, using 'manual' as the trigger and 'Excel-add a row into a table' as an action shown below.

Here are some test scenarios to help know what **bleep** happened.

Scenario1. with no input in the manual trigger and no write in the 'Excel' action, the process worked well. sure, nothing needs to do.

Then Scenario 2, with no input in the manual trigger and add dynamic content provided by the 'manual' trigger into the columns. Guess what happened? Every time I inserted a new parameter into the action, the process could run successfully until I met with this parameter 'Postal code'. The error message shows itself.
At the same time, I checked the 'peer code' of the 'manual' trigger. I noticed that with more parameters introduced into the action, the metadata(JSON Format) of the trigger is changing. In a simple word, more parameters were pre-defined and set as 'required'. Take the code with before and after modification for an example,

(before)

{
    "kind": "Button",
    "inputs": {
        "schema": {
            "type": "object",
            "properties": {},
            "required": []
        }
    },
    "metadata": {
        "operationMetadataId": "25ce17df-d732-4da2-af34-b214dbd90071"
    }
}

(after)

{
    "kind": "Button",
    "inputs": {
        "schema": {
            "type": "object",
            "properties": {
                "key-button-date": {
                    "title": "Date",
                    "type": "string",
                    "x-ms-dynamically-added": false
                },
                "location": {
                    "type": "object",
                    "properties": {
                        "fullAddress": {
                            "title": "Full address",
                            "type": "string",
                            "x-ms-dynamically-added": false
                        },
                        "address": {
                            "type": "object",
                            "properties": {
                                "countryOrRegion": {
                                    "title": "Country/Region",
                                    "type": "string",
                                    "x-ms-dynamically-added": false
                                },
                                "city": {
                                    "title": "City",
                                    "type": "string",
                                    "x-ms-dynamically-added": false
                                },
                                "state": {
                                    "title": "State",
                                    "type": "string",
                                    "x-ms-dynamically-added": false
                                },
                                "street": {
                                    "title": "Street",
                                    "type": "string",
                                    "x-ms-dynamically-added": false
                                }
                            },
                            "required": [
                                "countryOrRegion",
                                "city",
                                "state",
                                "street"
                            ]
                        },
                        "coordinates": {
                            "type": "object",
                            "properties": {
                                "latitude": {
                                    "title": "Latitude",
                                    "type": "number",
                                    "x-ms-dynamically-added": false
                                },
                                "longitude": {
                                    "title": "Longitude",
                                    "type": "number",
                                    "x-ms-dynamically-added": false
                                }
                            },
                            "required": [
                                "latitude",
                                "longitude"
                            ]
                        }
                    }
                }
            },
            "required": [
                "key-button-date",
                "location"
            ]
        },
        "headersSchema": {
            "x-ms-user-name-encoded": {
                "title": "User name",
                "type": "string",
                "format": "byte",
                "x-ms-dynamically-added": false
            }
        }
    },
    "metadata": {
        "operationMetadataId": "1c4b2850-164a-417d-94a9-04baeff831e6"
    }
}

Hitherto we almost figure out what caused the problem: the introduction of new parameters( especially this one: postal code) changed the 'peer code' of the 'manual' trigger, while when we do some actual tests. The 'postal Code' provides a ‘Null’. that's why. So I deleted 'Postal Code' from the mapping. It worked well.

Scenario3. Hold on if you are confusing why there is another test occasion. From the above test, we already know we can undo the setup by deleting dynamic content. Power Automation auto-modify the metadata of the trigger for us( in fact we can't manage the peer code). But I found that when you bulk-add or bulk-delete parameters from the 'Excel' action, the automation doesn't work which means the peer code of the manual trigger keeps all the same. I do think this maybe a bug, anyone knows?

(The meta data setup of the trigger doesn't change whatever i do.)

Besides, I also have some problems posed waiting to be answered.

Ⅰ about the tokens provided by the 'manual' trigger, such as address/ Usermail, where does the information come from? I checked the Dataverse, there is an immense discrepancy between the accounts table and trigger info.

Ⅱ From MS Learn I know that any pre-defined token could be used to trigger an action, but it doesn‘t seem that way. what can we do if I want to act on the basis of 'Postal Code'? like, make a judgement or condition.

Thanks. It took me some time to write this article.

Hope it can do some help if you are confued by the same question/bug.

And any answer to above questions will be appreciated.