Menu
Feedback
Start here
Tutorials
Developer portal

Known Issues
Support Rules
Troubleshooting

Frequently Asked Questions
Announcements
Known issues
UI triggers separate requests for each key/field of an attachment
UI triggers separate requests for each key/field of an attachment
ID: 336371
Backlog
Published on 3/1/2024
Last update on 3/1/2024

Summary

When you set the value for an item attachment field through the UI, this triggers a request to update the orderForm, even if there are still more fields left. This request will then be processed, and the response with the updated orderForm.

In cases where the attachment has multiple open text fields, this may cause subsequent fields to be overwritten while you're typing their values. This happens because the update request will have been sent when this field was still blank, so it will also be blank in the response.

In cases where the item has a subscription attachment with multiple keys, it may trigger an error message like "unable to communicate with seller" / "não foi possível se comunicar com o seller". This happens because the subscription will expect multiple keys to have been filled, but the first request will only have sent one.

Simulation

Create an attachment with at least two keys/fields. Add an item linked to this attachment to your cart, then add the attachment. Finally, set the value for one field, and observe the behavior that follows.

Workaround

N/A

Contributors
2
Photo of the contributor
Photo of the contributor
+ 2 contributors
Contributors
2
Photo of the contributor
Photo of the contributor
+ 2 contributors
On this page
Still got questions?
Ask the community
Find solutions and share ideas in the VTEX community.
Join our community
Request support from VTEX
For personalized assistance, contact our experts.
Open a support ticket
GithubDeveloper portalCommunityFeedback