Dataflow Gen2 parameter works with current value but fails when passed from Fabric Pipeline

Hi eyeampraveen​,
Thanks for reaching out to the Microsoft Fabric Community forum.

Please check the following to troubleshoot the difference between the current parameter value and the value supplied by the pipeline:

1.    Verify public parameter configuration: Confirm that the Dataflow Gen2 supports CI/CD and that Enable parameters to be discovered and override for execution is enabled. In the pipeline's Dataflow activity, verify that APIKey is configured with the expected parameter type and value.

2.    Verify parameter availability: Add a temporary diagnostic query that checks whether APIKey is non-null and nonempty. To verify the supplied value, compare it against the expected value using a secure method. Avoid displaying or logging the API key.

3.    Inspect the SOAP response: Verify that the HTTP response contains the expected SOAP XML before applying XML navigation. This can help identify whether the issue occurs during the web request or subsequent XML processing.

4.    Review detailed run logs: Open the Dataflow Gen2 item's Recent runs and download the detailed logs. Microsoft notes that the error information displayed in the pipeline's Dataflow activity might be incomplete.

Compare the successful run using the parameter's current value with the pipeline-triggered run to identify differences in parameter configuration, request construction, or response handling.

For more details, please refer to the below Official Microsoft Documentation :
•  Use public parameters in Dataflow Gen2 (Preview) - Microsoft Fabric | Microsoft Learn
•  Web.Contents - PowerQuery M | Microsoft Learn
•  Dataflow activity - Microsoft Fabric | Microsoft Learn

I hope this helps. Please feel free to reach out if you have any further questions.
Thank you.