We're exploring an Apsona trial right now and I was wondering if it is possible to nest sublists.
Particularly, we would like to merge documents on for multiple accounts that list their opportunities and each opportunity has a sub object to relate it to multiple campaigns, so we'd like to list the campaigns as a comma-separated list in one table row for each opportunity.
I found the documentation for a comma separated list (https://www.apsona.com/pages/sfdc/doc/doc-merge-combine-list-fields.html), but it doesn't mention whether it would work inside a table and when I tried it out I didn't see the list group option, just the table group option. So, I wanted to check if it is even possible to do that or if I just set it up wrong.
Hi @Katherine West, these use cases can be complex, so to really identify whether Apsona can get you exactly what you want, I feel it deserves a live conversation. We offer twice-weekly office hours where we can talk through your use case, share screen, and figure it out together. Here are the details:
"Tuesdays 8am PT/ 11am ET and Thursdays 10 am PT / 1 pm ET*** - no registration required - join via: bit.ly/ApsonaHours
***no hours on the third Thursday of each month due to our webinar schedule***"
But to provide a bit of high level info:
Technically speaking, if you are truly trying to create a second sublist from a data source, that is nested under a parent sublist, that is nested under a Top Level object: you can't do this in Apsona. Apsona's sublists allow for a top level parent (ie: Account) with a child sublist (opportunity). But some creative ways around this are:
- Use our grouping features. For example, you'd create a sublist of your custom campaign child object, but this sublist would display opportunity data along side the campaign data. You'd then group your custom campaign sublist by the opportunity data so that it looks like a sub-sublist. And your top level parent would be an opportunity report, but it would only include account data, so that you get the result of what looks like an Account based document, that has opp info and campaign child info.
- Use multiple independent sublists:
- Account would be the top level parent.
- One sublist would be a list of opps
- Another sublist below would be the child campaign object, that can be grouped in the same manner as above
- This doesn't nest the data as I imagine you'd like, but it would allow for true multiple sublists based on independent data sources
- Use a rollup tool to concatenate the campaigns into a comma separated list in a field on the opp and display that in an opp sublist as a merged field.
- There are probably some other ways.
I'd be happy to talk it out further during our office hours!
