从Logic Apps触发带参数的Azure Data Factory管道问题求助

Hey there! I’ve run into this exact issue when I was starting out with Logic Apps and ADF—nothing’s more frustrating than watching your pipeline run but ignoring the parameters you’re trying to send. Let’s break down the most common fixes that should get this working for you:

1. Start with the Logic Apps Visual Designer (Don’t Jump to Raw JSON First) #

Skip editing the JSON directly initially—use the visual designer to configure the "Execute Pipeline" action properly:

• Select your ADF instance and target pipeline.
• Once the pipeline is selected, the Parameters section will appear (if your pipeline has defined parameters).
• Manually add each parameter you want to pass, then map it to your Logic Apps value (like a workflow variable, trigger input, or static text).

This ensures the underlying JSON is generated with correct syntax, avoiding easy-to-miss mapping errors that come with manual JSON edits.

2. Verify the Correct JSON Structure (If You Do Edit It) #

If you need to tweak the raw JSON, make sure your parameters are nested correctly under the body → parameters object of the ADF action. Also, double-check that parameter names exactly match what’s defined in your ADF pipeline (they’re case-sensitive!). Here’s a working example:

"actions": {
  "Execute_My_ADF_Pipeline": {
    "type": "ApiConnection",
    "inputs": {
      "body": {
        "parameters": {
          "SourceFilePath": "@triggerBody()?['filePath']",
          "TargetDatabaseName": "@variables('targetDB')"
        }
      },
      "host": {
        "connection": {
          "name": "@parameters('$connections')['azuredatafactory']['connectionId']"
        }
      },
      "method": "post",
      "path": "/pipelines/@{encodeURIComponent('MyTargetPipeline')}/createRun"
    }
  }
}

Note: Parameters belong in the action’s body object, not the top-level triggers section of your Logic Apps workflow.

3. Confirm ADF Pipeline Parameter Setup #

In your ADF pipeline:

• Go to the Parameters tab (not the Triggers tab) and ensure the parameters you’re passing are defined here with the correct data type.
• Make sure your pipeline activities actually reference these parameters (e.g., in a Copy Activity’s source path, use @pipeline().parameters.SourceFilePath instead of a hardcoded value). If the parameter isn’t used anywhere, you might not notice it’s missing—but if it’s used and still shows the default, that means the value isn’t coming through from Logic Apps.

4. Debug with Run History #

• In Logic Apps: After running the workflow, open the run history, find the "Execute Pipeline" action, and check the Inputs section. You should see your parameters listed here with the values you intended. If they’re missing, the issue is in Logic Apps’ configuration.
• In ADF: Go to the pipeline’s run history, select the run triggered by Logic Apps, and check the Parameters tab. This shows exactly what values ADF received. If it’s displaying defaults, the parameters weren’t sent correctly from Logic Apps.

5. Watch for Common Pitfalls #

• Case Sensitivity: ADF parameter names are case-sensitive—sourcePath is not the same as SourcePath.
• Data Type Mismatch: If your ADF parameter is a string, make sure the value from Logic Apps is also a string (e.g., convert numeric values to strings first if needed). Mismatched types often cause parameters to fall back to defaults.
• Triggers vs. Pipeline Parameters: Since you’re triggering the pipeline from Logic Apps, you don’t need to configure parameters in ADF’s triggers—focus solely on the pipeline’s own parameters.

内容的提问来源于stack exchange，提问作者Mike R