Expand nested properties on nodepicker Content API
Hi,
For some context, I am new to umbraco. Primarily a nodejs based developer coming from Strapi - I already much prefer Umbraco having only used it for a week!
I am having issues with expanding the properties object on my content delivery api response.
I have Blog Article Document which is child of Blog Document. Inside the Blog Article Document, I have a node picker for Tag field so author can attach tag(s) to that specific blog article.
I also have Global Resources Document which houses these said Blog Tags which that also contains a further nested Document Type called Tag.
When fetching .../content/item/blog?expand=all the picked Tags are not pulling through, but the other deeply nested properties in response do show - see screenshot attached.
Upon further inspection of the docs, it appears you can only go 1 level with related node pickers - is there any option to expand this to say 2 or 3 - appreciate it may affect query performance.
Yeah I saw you could do this, but ideally wanted to leverage expand=all as my contents contain a lot of nested pickers, so having to manually add all attributes into the url would result in a nightmare.
Expand nested properties on nodepicker Content API
Hi,
For some context, I am new to umbraco. Primarily a nodejs based developer coming from Strapi - I already much prefer Umbraco having only used it for a week!
I am having issues with expanding the
propertiesobject on my content delivery api response.I have Blog Article Document which is child of Blog Document. Inside the Blog Article Document, I have a node picker for Tag field so author can attach tag(s) to that specific blog article.
I also have Global Resources Document which houses these said Blog Tags which that also contains a further nested Document Type called Tag.
When fetching
.../content/item/blog?expand=allthe picked Tags are not pulling through, but the other deeply nested properties in response do show - see screenshot attached.Any help and/or pointers is much appreciated!
Upon further inspection of the docs, it appears you can only go 1 level with related node pickers - is there any option to expand this to say 2 or 3 - appreciate it may affect query performance.
Cheers.
Please check docs here
it is mentioned that you should be able to do nested expansion with syntax like the below
Yeah I saw you could do this, but ideally wanted to leverage
expand=allas my contents contain a lot of nested pickers, so having to manually add all attributes into the url would result in a nightmare.is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.