Skip to main content

Notifications

Power Automate - Building Flows
Unanswered

Child flow suddenly requiring more inputs than defined

Posted on by 26

I have a child flow that requires the following inputs to be defined

 

image.png

 

However, when calling this flow from another "parent" flow additional fields are requested and the call fails because I haven't populated them (even though the location field isn't mandatory)

tidedbryant_0-1682504990336.png

 

Viewing the code for the trigger on the child flow does show these fields, but as you can see the interface doesn't show them within the Child flow. This doesn't feel correct, has anybody experienced this and knows of a fix?

 

{
 "kind": "Button",
 "inputs": {
 "schema": {
 "type": "object",
 "properties": {
 "text": {
 "title": "Update type from parent flow",
 "type": "string",
 "x-ms-dynamically-added": true,
 "description": "Please enter your input",
 "x-ms-content-hint": "TEXT"
 },
 "number": {
 "title": "id from parent flow",
 "type": "number",
 "x-ms-dynamically-added": true,
 "description": "Please enter a number",
 "x-ms-content-hint": "NUMBER"
 },
 "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
 },
 "postalCode": {
 "title": "Postal code",
 "type": "string",
 "x-ms-dynamically-added": false
 }
 },
 "required": [
 "countryOrRegion",
 "city",
 "state",
 "street",
 "postalCode"
 ]
 },
 "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": [
 "text",
 "number",
 "key-button-date",
 "location"
 ]
 },
 "headersSchema": {
 "x-ms-user-name-encoded": {
 "title": "User name",
 "type": "string",
 "format": "byte",
 "x-ms-dynamically-added": false
 },
 "x-ms-user-email-encoded": {
 "title": "User email",
 "type": "string",
 "format": "byte",
 "x-ms-dynamically-added": false
 },
 "x-ms-user-timestamp": {
 "title": "Timestamp",
 "type": "string",
 "x-ms-dynamically-added": false
 }
 }
 },
 "metadata": {
 "operationMetadataId": "xxx"
 }
}

 

 

  • Rajat Awasthi Profile Picture
    Rajat Awasthi 37 on at
    Re: Child flow suddenly requiring more inputs than defined

    Hi @tidedbryant ,

     

    please refer another post with proposed solutions for the same issue

    https://powerusers.microsoft.com/t5/General-Power-Automate/Run-a-Child-Flow-Action-now-has-required-Fields-Date-Full/td-p/1516606

     

  • diezvai Profile Picture
    diezvai 10 on at
    Re: Child flow suddenly requiring more inputs than defined

    Hi @tidedbryant.

    I have exactly the same issue here - did you find any solution?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

October 2024 Newsletter…

October 2024 Community Newsletter…

Community Update Oct 28…

Power Platform Community Update…

Tuesday Tip #4 How to Conntact Support…

Welcome to a brand new series, Tuesday Tips…

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 142,733

#2
RandyHayes Profile Picture

RandyHayes 76,308

#3
Pstork1 Profile Picture

Pstork1 63,750

Leaderboard