IRRDC
IRRDC
@walleford I just managed to create several levels of nested PropertyFieldCollectionDataHost. I don't know if it is what you are looking for but maybe it helps you along: I have...
Do you specifically want to access the first item here? this.properties.gridItems[0].dropData The gridItems collection will only have updated values once the control closes. To access the gridItem that matches the...
Yes, you are nesting to custom renders, each with a signature of (field, value, onUpdate, item, itemId, onError). If you change the parameter names in the signature of the nested...
Yes. In your code snippet you have to change `onCustomRender: (field, value, onUpdate, item, itemId, onError)` to `onCustomRender: (field, value, onUpdate, subItem, itemId, onError)` and `value: item.dropData` to `value: subItem`...
Sorry, I was thinking in too many nested layers just then. The code I'm working on right now is messing with my head. You don't need to rename item, set...
@walleford I'm just using `onChanged: (items) => { onUpdate(field.id, items); },` in the nested PropertyFieldCollectionDataHost.
@walleford I'm sorry but I don't see what is wrong with your code.
> Hi @IRRDC, > > Did you have the chance to repro this? Hi @michaelmaillot, I'm still getting the results sub-property for some lists when using the DynamicForm within my...
I just wrote the same feature and then I found this :-) Is it going to be included in a release build soon?
@GuidoZam I tested your code and would suggest that you remove these two lines:  since they lead to duplicate labels and make the field always required. Before removing them:...