Azure / LogicAppsUX

https://learn.microsoft.com/azure/logic-apps
MIT License
77 stars 84 forks source link

Issue using parameters from dynamic input in dynamic output payload #3709

Closed siddharth-ms closed 11 months ago

siddharth-ms commented 1 year ago

Describe the Bug with repro steps

We have a manifest like below: Screenshot 2023-11-16 200328 Where some input parameters are coming dynamically (marked red), We are unable to use those dynamic input parameters (which are not present on as static input, but appears after a dynamicInvoke call), in dynamic output parameter values in outputs (marked yellow). For example, fcName below is a parameter dynamically created by selecting RFC. This parameter (rfcName) is not being passed to the input payload of dynamic output call.

Screenshot 2023-11-17 093113

Below is the raw manifest:

{
  "inputs": {
    "type": "object",
    "properties": {
      "operationType": {
        "type": "string",
        "title": "Operation Type",
        "description": "Operation Type to Generate Schema.",
        "default": "RFC",
        "enum": [
          "BAPI",
          "RFC",
          "IDoc",
          "tRFC"
        ]
      },
      "fileNamePrefix": {
        "type": "string",
        "title": "File Name Prefix",
        "description": "File Name Prefix for Generate Schema."
      }
    },
    "required": [
      "operationType"
    ],
    "x-ms-dynamic-properties": {
      "dynamicState": {
        "extension": {
          "operationId": "getSchemaInputSwagger",
          "parameters": {}
        },
        "isInput": true
      },
      "parameters": {
        "operationType": {
          "parameterReference": "operationType"
        }
      }
    }
  },
  "inputsLocation": [
    "inputs",
    "parameters"
  ],
  "isInputsOptional": false,
  "outputs": {
    "type": "object",
    "properties": {
      "body": {
        "x-ms-dynamic-properties": {
          "dynamicState": {
            "extension": {
              "operationId": "getSchemaResponseDyanmicSchema",
              "parameters": {}
            }
          },
          "parameters": {
            "operationType": {
              "parameterReference": "operationType"
            },
+            "rfcName": {
+             "parameterReference": "rfcName"
+          },
            "fileNamePrefix": {
              "parameterReference": "fileNamePrefix"
            }
          }
        }
      }
    }
  },
  "isOutputsOptional": false,
  "settings": {
    "secureData": {},
    "trackedProperties": {
      "scopes": [
        "Action"
      ]
    }
  },
  "includeRootOutputs": false,
  "connectionReference": {
    "referenceKeyFormat": "serviceprovider"
  },
  "statusBadge": {
    "name": "Production",
    "description": "Production"
  },
  "operationOptions": "None"
}

Is this type of call supported?

What type of Logic App Is this happening in?

Standard (Portal)

Are you using new designer or old designer

New Designer

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

Workflow JSON

No response

Screenshots or Videos

No response

Browser

Edge

Additional context

No response

AB#25864112

preetriti1 commented 1 year ago

This scenario is never supported, all dynamic calls made either for inputs or outputs must depend on static parameters in the swagger/manifest

siddharth-ms commented 1 year ago

Are there plans for supporting those?

hartra344 commented 1 year ago

@siddharth-ms since you're internal, let's talk offline after thanksgiving and see what you're needs are exactly and if there's another way to achieve the same thing.

hartra344 commented 11 months ago

linking to #3708 for discussion

hartra344 commented 11 months ago

linking to #3707 for discussion since these are all for a single scenario

siddharth-ms commented 11 months ago

Discussed offline this scenario is not supported. Feel free to close it