Forum Discussion

12 Replies

  • v-sathmakuri's avatar
    v-sathmakuri
    Community Support

    Hi ksurujon ,

     

    Could you please confirm the above asked questions, so that we can check to see whether the issue is.

     

    Thanks!!

    • priyanshmeena96's avatar
      priyanshmeena96
      New Member

      If you want it to sound a bit more formal, I can also help with that.

  • ksurujon Can you post a screenshot of your configuration with the error? Documentation about these features may be inaccurate in some scenarios.

  • v-sathmakuri's avatar
    v-sathmakuri
    Community Support

    Thank you apturlov  and GilbertQ  for the prompt response.

     

    Hi ksurujon ,

     

    Thank you for reaching out to fabric community.

     

    Could you please confirm on the below : 

     

    1. Which Fabric item type you're running the job for (for example, Notebook, Pipeline, or Spark Job Definition)?
    2. The request body you're using?
    3. The complete error message or response returned when parameters is used as a top-level property.

    Thanks!!

  • you meant something different by "MS" (for example, another abbreviation), let me know what "MS" stands for and I can suggest the most natural wording.

  • Yes, this looks like a documentation/API mismatch. If parameters only work under executionData, the docs may be outdated or incorrect. Report it to Microsoft with the failing request and working example so they can confirm whether it’s a known issue.