Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Screen Shot 2565-08-08 at 14.45.58.png

Screen Shot 2565-08-08 at 14.45.38.png

Screen Shot 2565-08-08 at 14.46.10.png

Hey,
I was wondering on how to deal/set more complex parameter structures in Prefect Orion. E.g. when I have lists ore nested models, I can’t set them on the UI at all.

example_flow.py

Building this via `prefect deployment build ./param_example.py:example_flow -n example_flow -o example_flow-deployment.yaml`
And then applying via:
`prefect deployment apply 'example_flow-deployment.yaml'`

It seems for lists the UI is buggy, it looks like it’s supposed to be able to select lists, but in the end it only takes a string value

great example to reproduce and I was indeed able to reproduce -- thanks for raising that and I'll open an issue

<@ULVA73B9P> open "UI interprets parameters of type list as strings"

<https://github.com/PrefectHQ/prefect/issues/6287>

for now as a workaround, when you set those on the deployment YAML, it should work
```parameters: {}```

yep, it works setting them in the YAML. I also realized doing this:
```def example_flow(params: ExampleParams = ExampleParams()):```
sets up the default params directly, so also a good workaround for now

nice work and thanks again for reporting that UI bug