I've created an asset listing so I can get a list of all users in a particular group. That group has a metadata schema applied to it so that all those users have a Group variable attached to them. In the asset listing bodycopy thing I have the following line
"%asset_metadata_first_name% %asset_metadata_last_name%","%asset_metadata_Group%","%asset_metadata_email%"
but only the asset_metadata_Group keyword is working because the others aren't really metadata. So what keywords should I use to get the other attributes that I need?
Try asset_attribute_first_name, asset_attribute_last_name and asset_attribute_email.
Excellent, that does exactly what I want. But if you give a mouse a cookie......
Now I'm wondering if there is a way to get the user's group (when users are being pulled into an asset listing). that way I could dispense with the metadata schema that I cooked up to make that data available. In the case of this asset listing I could hard code it into the output, since it is set to only get from one node I could just type the name of that node into the results. But I imagine there should be a more Matrixy way to do it. If you could point to the asset-attribute.... stuff in the documentation you'll probably prevent me from asking a few more keyword related questions.
[quote]Excellent, that does exactly what I want. But if you give a mouse a cookie…
Now I'm wondering if there is a way to get the user's group (when users are being pulled into an asset listing). that way I could dispense with the metadata schema that I cooked up to make that data available. In the case of this asset listing I could hard code it into the output, since it is set to only get from one node I could just type the name of that node into the results. But I imagine there should be a more Matrixy way to do it. If you could point to the asset-attribute… stuff in the documentation you'll probably prevent me from asking a few more keyword related questions.[/quote]
There is no keyword for this as an asset can have many parents. But, if you know that your users only have one parents, you could try using a nested asset listing in the type format which looks up the tree one level and sees its parent. But, not you have the problem of all of the returned assets showing their same parent…