Open mmmonsanto opened 1 month ago
hi @mmmonsanto, please note that the control will try to reflect the related records from the relationship, not from JSON. JSON objects are just a convenient way to access those selected items. This only happens in the frontend, when you open the form, the JSON will be updated to reflect related records.
changing JSON manually doesn't change the related records. If you want to remove all selected items from backend (plugins/flows), your plugin should disassociate all related records instead.
hope this helps!
Component [DCE PCF Components]
Component name and version
A clear and concise description of what the bug is. I had and polylookup fields in case entity and everytime the case updated it will create an record to a Case Tracking History and one of the field is copying a record from the polylookup field in Case Entity into the Case Tracking History entity.
Bugs are the following:
Expected behavior
JSON value should be the values to load in the configured polylookup field.
Actual behavior
JSON value is modified/changed but the original/current record prior on changed still be displayed in the form.
Screenshots selected a value for Manager field:
when the record is saved, it has a correct JSON value in the field
after, updating the value to NULL value in the backend and then reload the value in the form, it is still be displayed. screenshot from backend that the record is NULL
In the form, the current record prior to update the value to NULL will be displayed instead to an empty value
Additional context
I am using Dynamics 365 CRM, Power Platform environment.