Hello,
Just like a contact/company/deal property, is it possible to see in some place where a list has been used ? For example, for which email recipients it was used and by which workflow it is used/updated ?
Thank you,
Hello,
Just like a contact/company/deal property, is it possible to see in some place where a list has been used ? For example, for which email recipients it was used and by which workflow it is used/updated ?
Thank you,
Hi @Anonymous
Sadly this is not possible at the moment.
I recommend creating as few lists as possible, naming them carefully and organising them in folders to keep track of things.
Not easy, I know, list can get out of hand pretty quick.
Hope this helps.
You can hover over the number in the Used In column in the lists view to see which other lists, reports and workflows a list is used in - I find that really helpful, especially for Workflows. But you can’t see the emails that may have used the list as a recipient list.
Great tip @Leslie_Vanco!
The new list tool doesn’t allow you to hover over the number to identify other lists/workflows. It would be great if this did this again, along with emails as it’s really important with larger, Enterprise users that we can determine where the lists are used in emails in order to delete lists if they are not necessary/out of date, and/or send out to the regions to confirm what can be deleted.
So, I want to change a list from 30 days, to 90 days, but I cannot see any way if the list is used in a workflow? That could blow up kpi, reports, processes, alerts, in so many ways. Just a simple change. How is it not mandatory to show if a list is used in a workflow that could impact 10s of 1000’s of records?
@SVoge
Oddly, I can’t find an edit or delete option for my original post, but I would like to amend and provide a solution.
I tagged Sam Voge, an awesome HS rep, and she pointed out that the HS List has an Activity tab, and if you click it, it shows the ‘in use’ situations and even the history of former in use. I’m surprised I didn’t hear that in the 3 threads I checked about this issue.