I’m hopeful someone might have a solution for this issue I’m facing. I’m struggling with how to render nested custom fields in Bricks. Here’s a simplified version of the scenario. I have a page with ACF custom fields ( let’s call this page the “Front-End Page”). Inside of this page, I have a section template with its own set of custom fields, which include dynamic tags that I’d like to pull data from the Front-End Page. For example, let’s say the Front-End Page has a custom field called {my_datapoint}. Using the dynamic tag {acf_my_datapoint} to pull in custom field data works just fine on the page. In my section template, however, I’m nesting {acf_my_datapoint} inside of a custom field but when I render the Front-End Page, the dynamic data tag blanks out. Is possible for a section template custom field to pull dynamic data sourced from the Front-End Page?
This is a bit hard to understand. Maybe you could post screenshots of your setup from inside the builder.
Cheers Suat
Hi Suat - Thank you for the response. I drew up a quick diagram of what I’m trying to accomplish. Hopefully this is helpful. This will be used across hundreds of pages so I’m trying to make this as scalable as possible. If you have any suggestions on how make this work I’m all ears! Thank you.
This should work right out the box, since bricks should understand that the section template is being displayed in the context of the page Frontend-End Page.
it surprises me that this doesn’t work out of the box.
The display condition for your acf field is all pages? or did you also put it on bricks_templates?
Maybe test wrapping the section template in a query-loop, to see if that works. I know this won’t work programmatically, but then you could be sure, that it just has a wrong context.
Hi Suat - Thanks for your help. I was hoping it would work out of the box as well. The display condition for acf fields are are set to show on associated pages, templates, and custom post types. In general, the front-end page can bring in and render custom fields from templates fine… the issue is when I nest a custom field inside a custom field, like I did in the section template in the above example. If you have any other ideas please do let me know. I’m no ACF expert by any stretch but I’m certain this is a common use case and that there is a solution.
Also, FYI, the section template is indeed query looped. I also tried it without the query loop. Neither method will render the nested custom field unfortunately.
This is a bit obscure to solve just from reading your text. I’d need to see the backend ACF-Fields and the implementation (with structure-panel and bricks settings) to fully understand it.
If you feel comfortable you could pm me credentials for the site, or post some more in depth pictures (not schematics), so I can understand the problem better.
A picture tells often more than 1000 words 
Sounds like they are supposed to be related, correct? If so, did you build the relationship between the post types?