This happens when two or more forms in the same bundle share a field with the same name. Because Quik! uses a standardized field definition across all forms, any field with a matching name will prefill with the same value on every form in the bundle — even if you need different values on each one (for example, bundling forms for two different account holders, or including two copies of the same form for multiple beneficiaries).
If you're generating forms through our API, this is resolved using a feature called Form Group Instances, which lets each form in the bundle keep its own distinct value instead of sharing one across the whole package. This is configured in the request your integration sends to us — specifically by structuring the QuikFormID value to separate form groups and appending instance suffixes to the relevant field names.
If your team needs help understanding how to structure this for your specific bundle, reach out to support@quikforms.com with:
- The forms you're trying to bundle together (form names and/or Quik! Form IDs)
- Which fields are conflicting
- What values you expect to appear on each form
We can point you to the right documentation and answer any technical questions, though the implementation itself happens on your integration's side.
If these are your own proprietary forms, we can also update the conflicting field on one of the forms and remap it to another suitable field, removing the conflict entirely. Let us know if you'd like us to take this route instead.
If this involves a public library form, the fix isn't as straightforward, since any change affects everyone using that form. In this case, we'll need to do some research and look into the best way to resolve it before making any changes.