What's new in 0.9.0
Multi-select answers work end to end: they save, they can add to what a record already holds, and they survive a prefill.
Flux Forms 0.9.0 is about questions with more than one answer.
A checkbox group could always be asked. What it could not reliably do was reach a Salesforce multi-select picklist and come back out again. This release closes that round trip and adds a choice about how the answer lands.
Checkbox answers now reach a multi-select picklist
Mapping a checkbox group onto a multi-select picklist used to fail the moment the form was submitted. The selection was written in a shape the field rejects, so the action errored and the whole submission segment rolled back — nothing was saved, not the record and not the steps after it.
The selection is now joined the way Salesforce stores a multi-select field, so:
- Ticking several boxes stores several options.
- The stored value prefills back into the same ticks later. What goes in comes out.
- Ticking nothing clears the field.
- A single-value target still works while the visitor ticks at most one box, and still fails with a message naming the field when they tick two or more. That was already the rule; it is unchanged.
Nothing to configure. Existing forms simply stop failing.
Write mode: overwrite, or add to what is already there
A field-mapping row that targets a multi-select picklist now shows a Write mode picker:
- Overwrite — the default, and exactly how every mapping made before this behaves. The answer replaces whatever the record holds.
- Add to existing — the answer is merged into what the record already holds. Stored options keep their place and their spelling, only genuinely new ones are added, and re-ticking one that is already stored changes nothing. Tick nothing and the field is left untouched rather than emptied.
Reach for Add to existing when several forms — or repeat submissions by the same person — each contribute part of a larger set: interests, skills, shift preferences. Reach for Overwrite when the form asks the visitor to confirm the complete, current set.
Two things worth knowing:
- Add to existing can only add, never remove. If a visitor must be able to un-tick something, use Overwrite.
- On a Create record action the picker has no effect. A brand-new record holds nothing to add to.
The picker appears on multi-select targets only, because no other field type can sensibly be added to. Point Add to existing at anything else and the action reports it in plain words rather than writing something wrong. See Submission actions and Submissions and errors.
Prefilled ticks stay ticked
A checkbox group prefilled from a record lost every prefilled selection the moment the visitor ticked one more box: the answer came back as just the box they clicked, and the rest was silently dropped on submit. The boxes even looked right until that first click, which is what made it easy to miss.
Ticking now adds to the prefilled selection instead of replacing it. This affects visitors on live forms, so there is nothing to change and nothing to republish.
Nothing you already had changes
- Mappings authored before this release carry no write mode, and a missing write mode means Overwrite — the behaviour they already had.
- Single-value targets, flows, Apex actions and every other action type are untouched.
- An upsert without an external id field also stopped inserting a duplicate along the way.
Where to read more
- Submission actions — the Write mode picker, and what a checkbox group needs from its target field
- Data mapping and prefill — how a multi-select field prefills back into ticks
- Submissions and errors — the two new messages a wrong write mode produces
