Not entirely sure if the right repo to raise an issue, but it seems to be a UI glitch to me. When creating an object using property assignment, empty list inputs get converted to null - in the example below we should rather get 3 valid objects and ignore 2 empty lists rather than getting 5 objects, 2 of them invalid:
Description:
Not entirely sure if the right repo to raise an issue, but it seems to be a UI glitch to me. When creating an object using property assignment, empty list inputs get converted to
null
- in the example below we should rather get 3 valid objects and ignore 2 empty lists rather than getting 5 objects, 2 of them invalid:Test file(s):
On SharePoint