[MGNLPN-612] Multivalue value field does not accurately update after changes Created: 16/Oct/18  Updated: 18/Oct/22  Resolved: 07/Jan/22

Status: Closed
Project: Magnolia Personalization
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: James Spence Assignee: Yen Lac Tue
Resolution: Won't Fix Votes: 0
Labels: VN-Maintenance, maintenance, to-verify
Remaining Estimate: Not Specified
Time Spent: 3d 3h 13m
Original Estimate: Not Specified

Attachments: PNG File image-2018-10-16-15-46-51-244.png     PNG File image-2018-10-16-15-47-52-296.png     File multivalue-bug.mp4    
Issue Links:
causality
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: AuthorX Support
Sprint: AuthorX 1
Story Points: 2
Team: AuthorX

 Description   

When configuring a trait with the following valueField configuration:

 

When modifying the value inside of the preview app, the first time I add a value, it isn't reflected in the trait. Every subsequent modification shows me the previous state, before my modification. For example:

will not have any values specified on the item. If I then modify the value to "bar" in the text field, the item's value will then be a list, with a single value: "foo".

 

This issue is present on both 5.5.12 and 5.6.8. It appears specifically when I use a multifield in the value field.

 

To reproduce:

1) Create a fresh magnolia instance on 5.5.12 or 5.6.8

2) Configure a trait that uses a multivalue field under the "valueField" configuration

3) Open the preview app and add a value for that trait. Observe that no value is actually set in the parameter converter.

4) Add a second value or modify the original value, thus triggering another submit. Observe that the first value is what appears in the parameter converter now, rather than the updated value.



 Comments   
Comment by James Spence [ 17/Oct/18 ]

Please view the attached video screen cap of the issue and my debugging of the issue.

Comment by Viet Nguyen [ 26/Aug/21 ]

Some possible workarounds:

  1. Use our Properties endpoint with REST call to update the property or using a content app to edit it.
  2. You can reference to our Tours app configuration of a multivalue property which is editable using its detail subapp. Link of the configuration here for your reference.
  3. Use Groovy script to set the property multi-value.
Generated at Mon Feb 12 06:39:22 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.