FormFieldExtensionJS: Issue after migrating from 2023.1.2 to 2023.1.3

0

Hi
We will analyze it.
Is this just part of the FormFieldExtensionJS UI or do you have some business logic as well?
If you have logic, are you using your own TValue model: FormFieldExtension<TConfig, TValue>?

Hi Tomasz,

thanks for the feedback.

I do have a business logic class, but no "official" model. I just converted the JSON object to a string in the REACT component and then deserialized the string in the backend again.

I used this simply to transfer the information to the backend. I didn't even save the value.

public override Task VerifySaveRestrictionsAsync(ControlSaveRestrictionsParams<FormFieldExtensionContext> args)
{
var fieldValue = args.Context.CurrentFormField.GetValue() as string;
// Clear the token.
args.Context.CurrentFormField.SetValue(null);


As soon as I find the time, I will test it using a real model.

Best regards,
Daniel

Hi Tomasz,

thanks, as soon as I used the correct way it was working as expected. :)

In case someone else is stumbling upon this post I will post the changes. The numbers refer to those in the picture.

1. "Declare" the "Result" as an actual plugin value.
2. Changes to the Logic. ConverToControlTypeAsync would be different in another case. This works for me, as the value is never stored in the database
3. "newData" is the object which is passed to onChange
4. Change in the additional validator

Best regards,
Daniel