How to deeply populate (sub)components inside dynamic zone

[Bart_Lagerweij]

System Information

• Strapi Version: 4.0.3
• Operating System: Linux
• Node Version: v12.22.9

---

Hi all,

I like strapi very much.
It is highly flexible in using components inside components inside dynamic zones. But fetching this content seems to be hard…

I have a dynamic zone “Content”, that contains a lot of components.
But how can i pull all components with all information out of the api?

My content:

I have read the documentation about the populate parameter, but I need to deeply populate all components in the dynamic zone. Preferable without having to name everything I want inside the populate argument.

Is there a way that I can specify the number of population levels? I’ve read somewhere that this is 2 by default.

Or is there a way that I can pull out (in a separate request) all populated components found in dynamic zone “Content”?

Regards,
Bart.

[Deviant_Dev]

@Bart_Lagerweij

ferable without having to name everything I want inside the populate argument.

Is there a way that I can specify the number of population levels? I’ve read somewhere that this is 2 by default.

Or is there a way that I can pull out (in a separate request) all populated components found in dynamic zone “Content”?

I am struggling with this as well. Its so frustrating! For me everything is working until you have a component with components and then it doesn’t populate. Have you gotten it to work with nested components yet even if its manually?

I have an open github issue currently Deep Querying components in Dynamic Zone not working correctly · Issue #290 · gatsby-uc/gatsby-source-strapi · GitHub

[Bart_Lagerweij]

Nope, still looking for a solution…

[Deviant_Dev]

Maybe we will have luck with the gatsby conf happening. I am attending if you are not I will feedback here for you If I make any headway

[Bart_Lagerweij]

We don’t use gatsby (yet).
We (webleads) are looking to create a “hybrideCMS” with Strapi and ForkCMS…

[Edward_B]

this worked for me
?populate=*

[Bart_Lagerweij]

It does not work with dynamic zones and (sub)components.

Look at this example:

https://gist.github.com/bart-webleads/78112d23f18b63dd3bf92e8f7506f7a7

The compoment “blocks.image-left” looks like this:
Title (Text)
SubTitle (Text)
Body (Rich text)
Image (Media)
Link (Component)
Text (Text)
Hyperlink (Text)
Hint (Text)

In the api result you see that the component “blocks.image-left” only has the id, Title, SubTitle and Body field.

[mjtch-rll]

Hey Bart, if you’re still looking for a solution check-out this thread.

Looks like it worked for many people by editing strapi’s controller

Strapi V4 populate Media and Dynamiczones from Components

As we already know we can populate by field like “/articles?populate=tags,author”. But, if we have a media filed in author table (lets say an ‘avatar’ image) , it will not be returned in response. To fix this, we can just access it like this, “/articles?populate=tags,author.avatar” where avatar is the media field we want to populate in our nested author object. I do it for selective populate use cases. Been bummed about it for couple of days and found out this works by trial and error (smashes…

[Bart_Lagerweij]

Ah, will check that out, thx for pointing me to it

[David_Ortega]

Same issue here

[George_Washington]

Strapi needs a super simple way to populate everything all the way down multiple levels. May I suggest: populate=everything_dammit__yes_i_accept_the_consequences_of_my_actions

[Emil_Ricardo]

I have a dynamic zone “sections”, i use qs (npm i qs)

const queryPages = qs.stringify(
  {
    populate: {
      sections: {
        populate: "*",
      },
    },
  },
  {
    encodeValuesOnly: true, // prettify URL
  }
);

result

populate[sections][populate]=%2A