Fields going blank when using new "Save as Draft" feature

[Abbottronix]

We recently updated our instance and we now have the new "Save as Draft" feature on our catalog forms. However, when using this feature, we've noticed that one of our fields always goes blank when we open a saved draft. The field is in a variable set, however, we have two variable sets on the form, and the fields on the other variable set are fine when saved as draft. The first variable set is at the start of the form, whereas the variable set with the blank field is at the end, in case that makes any difference.

[Hitoshi Ozawa]

@Abbottronix Since you're using an updateset, you probably have a developer instance and a production instance.

Does "Save as Draft" not working in the developer instance. That is, if you don't use the update set, does the "Save as Draft" working?

Or do you have several developer instances and importing variable sets from other developer instance into yours?

If so, are all the developer instances in the same version as yours?

[Abbottronix]

Sorry I meant to write variable set not update set

[Hitoshi Ozawa]

@Abbottronix Tried it and it works are expected with no value going blank.

Tried with 2 mvrs set each with single line text and no ui policy nor client script.

Check if you have any ui policy or client script in the second variable set or on the catalog item form.

[kack l]

I also encountered the same problem, have you solved it?