This happens when I have fields that belong in a Folder (according to the api’s
/fields request) and then those fields get used as part of a hierarchy (using the mapping object).
There is a rendering error when I expand the folder, which looks like the attached image. The levels do not appear under the new hierarchy’s name, and I can’t seem to properly use the hierarchy.
Additionally there is a console error:
ERROR TypeError: Cannot read property 'length' of undefined
at b.nk (flexmonster.full.js:1845)
at b.UL (flexmonster.full.js:1844)
at b.update (flexmonster.full.js:1843)
at b.update (flexmonster.full.js:1884)
at e.open (flexmonster.full.js:1906)
at h.GV (flexmonster.full.js:1456)
I have resorted to not having the fields of this hierarchy in a Folder to prevent this error.
Also, a side question: Is it possible to re-map the field/hierarchy to a different folder using the mapping object?
Thank you for writing to us and giving us some time to take a deeper look at your question.
We’ve managed to reproduce the described behavior on our side and we have already passed this over to our developers. The fix will be made available with our upcoming release ETA Oct 19th.
Answering your second question, at the moment it is not possible to change the folder that the field belongs to – we would suggest sending the fields from the server-side grouped in necessary folders to begin with.
Please let us know if you have any other questions we can help you with.
We are glad to inform you that the issue with multi-level hierarchies and folders in the Field List was fixed.
This is included in the 2.8.18 version of Flexmonster: https://www.flexmonster.com/release-notes/
You are welcome to update the component: https://www.flexmonster.com/doc/updating-to-the-latest-version/
Please let us know if there is anything else we can help you with.
That’s great, I have checked and it works like a charm!