-
Type:
Bug
-
Status: Resolved
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Automation, Core
-
Sprint:nxFG 8.10.2
-
Story Points:3
When calling ListProperty.remove, during saveDocument the list of states is correctly shrunk to the new list size, but each complex list element is still viewed as "not dirty" so not written to storage. The end result is that the last list element is removed, which is incorrect.
This can easily be seen using the Blob.Remove operation, it always removes the last entry from the list.
- is related to
-
NXP-19261 Set vs Update for complex list elements
-
- Resolved
-