Cannot use Pattern Matching on Http Request Trigger

[alburgin]

Hi,

I am trying to create a flow triggered by http request which sends an email. I want to use validation to pattern match the inputs. When I add schema validation, it won't save with the following error: " The 'operationOptions' property is not allowed on the trigger when the workflow contains actions of type 'OpenApiConnection'.'."    Additionally, if I don't add schema validation but add the patterns into the json schema I get the following error when I try to save: 'The 'schema' property of trigger 'manual' inputs of type 'Request' at line '1' and column '577 contains 'pattern' or 'patternProperties' properties. 'Pattern' or 'patternProperties' properties are not supported in trigger json schema, trigger schema validation is enabled when operationOptions set to 'EnableSchemaValidation' or the workflow contains any actions of type 'OpenApiConnection'..'.  Is using patterns to validate the input strings to a web hook flow not supported?

Thanks!

[alburgin]

For more context, I am trying the following as the flow

With the following schema.

{

    "$schema": "http://json-schema.org/draft-07/schema",

    "$id": "http://example.com/example.json",

    "type": "object",

    "title": "The Root Schema",

    "description": "The root schema comprises the entire JSON document.",

    "required": [

        "imageName",

        "imageVersion"

    ],

    "properties": {

        "imageName": {

            "$id": "#/properties/imageName",

            "type": "string",

            "title": "The Imagename Schema",

            "description": "An explanation about the purpose of this instance.",

            "default": "",

            "examples": [

                "commonproxytestacr.azurecr.io/commonproxy"

            ],

            "pattern": "^[\\w.]*/[\\w]*$"

        },

        "imageVersion": {

            "$id": "#/properties/imageVersion",

            "type": "string",

            "minLength": 7,

            "title": "The Imageversion Schema",

            "description": "An explanation about the purpose of this instance.",

            "default": "",

            "examples": [

                "6.2004.17.0"

            ],

       "pattern": "^[0-9]*\\.[0-9]*\\.[0-9]*.[0-9]*$"

        }

    }

}

[RoryL]

Hi alburgin,

Thank you for your post to the community. I worked through the details for this issue but I am not seeing an obvious cause for the problem. We would like to get some more details about the issue to help better understand the cause of this problem. I would like to suggest that you create a support ticket with our team where we can further work to understand why you are seeing this issue. More information about how to do this is available here: https://docs.microsoft.com/en-us/power-platform/admin/get-help-support

Thank you,

Rory

[Priesh]

I'm having the similar error message as I'm trying to run get items from sharepoint action with HTTP request trigger. 

The error I get is:

Flow save failed with code 'ValueNotSupported' and message 'The trigger 'manual' at line '1' and column '673' is not valid. The 'operationOptions' property is not allowed on the trigger when the workflow contains actions of type 'OpenApiConnection'.'.

Any advice will be appreciated, thanks

[andrew1stein]

As of 2/8/2022 at least, In Power Automate, this error -

The 'operationOptions' property is not allowed on the trigger when the workflow contains actions of type 'OpenApiConnection'

... can also happen when you have schema validation turned *on* on an HTTP Request trigger action ("When a HTTP request is received").

(Presumably, changing *any* setting on the HTTP Request trigger in PA will cause the same error message - but I have not tested this).

Make sure to turn this, and possibly any other setting, off, if you had turned them on.

Why? I don't know. If you need to do schema validation for an incoming HTTP request in Power Automate, throw in a Parse JSON action after the HTTP request with the schema you expect, instead. 

Thanks,

Andrew 

[Priesh]

Thanks, for your message. I worked it out and it was schema validation, I turned it off.  

[MarcusBW]

Same issue here I guess pattern matching not supported - this seems a bit limiting.

Get the following error both with schema validation enable on the HTTP triger, and when trying to parse the JSON

ActionSchemaNotSupported. The 'schema' property of action 'ParseJson' inputs contains 'pattern' or 'patternProperties' properties. 'Pattern' or 'patternProperties' properties are not supported in the action json schema

[andrew1stein]

Turn *off* Schema validation and you should not get the error.

[MarcusBW]

I have turned off schema validation - thing is I WANT to catch and report on the errors per the schema validation and in particular invalid email address, invalid phone number.  regex and pattern matching would make this very easy and repeatable to validate a complex payload - if it was supported

[andrew1stein]

Agreed, if it was supported.

You can also do a Parse JSON (with schema validation but no pattern matching in the schema), and then use the regex() function in a foreach loop over each row of the output. Of course this is just a workaround and ideally pattern matching would be supported. Has anyone submitted this to the Requests / User voice? 

[chrismewes]

Anyone found a fix for this?  Still unable to use any of the settings on the Http Request Trigger

[GoodPanos]

I get this error message when I turn on "Suppress Workflow Headers on Response" and I have a Add a new row in  Dataverse action. Any help would be greatly appreciated.

[GoodPanos]

I found a workaround this.

I discovered that any settings your turn on the "When a HTTP Request is Received" trigger in a Flow that has any action other than the simple Compose or Variable actions, you will get the above mentioned error.

The workaround is to put your Flow in a solution and create a child Flow where you pass in all the data returned from the "When a HTTP Request is Received" trigger (the parent Flow). Now, in the child Flow you can use any action and you will stop getting the save error.