Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Store complex Provider Settings-value from Property Editor UI #1335

Closed
enkelmedia opened this issue Dec 16, 2024 · 1 comment
Closed

Store complex Provider Settings-value from Property Editor UI #1335

enkelmedia opened this issue Dec 16, 2024 · 1 comment

Comments

@enkelmedia
Copy link

enkelmedia commented Dec 16, 2024

I'm working on a WorkflowType with a setting where I would like to reuse an existing PropertyEditorUI-component.

In older versions of Umbraco Forms I could send a JSON value to the server to be stored as a string-property.

I'm trying to get this to work on v15.0.3 and I'm getting this error when the properties are validated:

image

It's probably an error from the model binder, since the value is a object and not just a string.

I've tried a couple of things:

  • To use the SupportsHtml-option but that did not work.
  • Change the property from string to List<MyType> (the stored value is an array). Did not work but would be really cool if it was supported.

Is there a way around this or would I have to create propertyEditorUi specifically Umbraco Forms?

The docs indicates that this should work:

Each setting type can have it's own user interface. So a string can use a text box but a more complicated JSON structure can use a more appropriate user interface.

Maybe you could use JSON.stringify if the value is a object?

Cheers!

// Markus

@enkelmedia enkelmedia changed the title Store complex value from Property Editor UI Store complex Provider Settings- value from Property Editor UI Dec 16, 2024
@enkelmedia enkelmedia changed the title Store complex Provider Settings- value from Property Editor UI Store complex Provider Settings-value from Property Editor UI Dec 16, 2024
@AndyButland
Copy link

Will respond to this and #1334 on the linked issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants