cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
alburgin
Employee
Employee

Cannot use Pattern Matching on Http Request Trigger

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!

12 REPLIES 12
alburgin
Employee
Employee

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

 
 
 

Flow.PNG

With the following schema.

{
    "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
Community Support
Community Support

 

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
Regular Visitor

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'.'.

 

Priesh_0-1642761830730.png

 

Any advice will be appreciated, thanks

andrew1stein
Employee
Employee

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.

 

andrew1stein_0-1644344717635.png

 

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 

 

 

 

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

MarcusBW
Frequent Visitor

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

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

MarcusBW
Frequent Visitor

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

 

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
Advocate I
Advocate I

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

GoodPanos
Helper II
Helper II

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
Helper II
Helper II

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.

Helpful resources

Announcements

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (3,319)