I’m using an asset listing to count remote child assets which uses the session variable: list_current_asset_id.
This suits my purposes well when nesting via a traditional ‘Nest Content’ container type within the asset’s contents where needed.
My question is - how would I nest this assist listing via the %globals_asset_contents:xx% keyword with the session var intact? There are some instances where I need to include this listing amongst code blocks where additional containers make it a bit clunky.
Is the dynamic root node value going to be sourced from the frontend asset you are viewing on the frontend?
If so, you should be able to just use %globals_asset_contents_raw:xxx% and on the dynamic parameters of the asset listing use Set Value and %frontend_asset_assetid% as the root node value. Or change assetid to metadata if it’s coming from there.
No not really. I’m trying to utilise asset IDs printed within an asset listing as the root nodes. My counter sits within the default format of this listing.
I gave the above a shot anyways (via global keywords + nesting), but as expected no dice.