Setting Workspace Property to Blank via UI does not propagate

[matthew-a-dunlap]

Describe the bug
If you have a field for your workspace and attempt to change it from a value to blank, the UI will not pass that info with the API request. The command will succeed but the field change will not take place.

In our installation we have a number of custom workspace billing fields that we have to change occasionally, and this issue stops us from being able to do that without editing via the database or direct API calls.

Azure TRE release version (e.g. v0.14.0 or main): v0.25

[marrobi]

@matthew-a-dunlap thanks Odd one. I've set copilot on it.

An alternative is we should look at migrating to RJSF 6 - https://rjsf-team.github.io/react-jsonschema-form/docs/migration-guides/v6.x%20upgrade%20guide/

Might find the issue gets fixed there.

[matthew-a-dunlap]

@marrobi Thanks for the quick investigation. End of day yesterday I tinkered on a solution with copilot in VSCode that I think is a bit more robust. It tracks the changes to forms and only sends data that has changed.

I've created a PR to pull those changes into the copilot branch that exists. I have a fair bit of experience with web UI work, but no experience with react etc. Let me know if there is a better way to propose changes like this :)

#4830

I will test the changes in my PR soon

[JC-wk]

Hi @matthew-a-dunlap have you seen this? rjsf-team/react-jsonschema-form#3728
especially this comment rjsf-team/react-jsonschema-form#3728 (comment)

You can use the uiSchema option ui:emptyValue to ensure the empty case falls back to the empty string instead of removing it from the formData.

[JC-wk]

Just wanted to provide a possible solution here for anyone searching in future. Be aware that this value overrides the "required" property rjsf-team/react-jsonschema-form#605 so it would potentially not be desirable to have it set everywhere.

  "uiSchema": {
    "your_property_name": {
      "ui:emptyValue": ""
    }

Note: Don't use the "overview" field for testing like I did, there is a bug as that value is overwritten in the ui, I will implement a fix.

[marrobi]

@matthew-a-dunlap @JC-wk so what do you think the solution is here? Is it a case of just modifying your specific template? If so can we close this?

[JC-wk]

IMO Yes just add this to your template and close this issue and PR

  "uiSchema": {
    "your_property_name": {
      "ui:emptyValue": ""
    }