Work.com
Leading Through Change with Data
COVID-19 Data Hub
COVID-19 Global Daily Tracker
Global Economy Data Track
Government Data Track
Healthcare Data Track
B-Well Together
Leading Through Change
Salesforce Care
Leading Through Change Blog
Trailhead Resources
AppExchange Resources
MuleSoft Resources
< Back to List
Mateusz Dąbrowski
_DataSourceName should show Entry Data Extension in Journey Builder
Journey Builder
_DataSourceName personalisation string, as per documentation, should show any audience object sent to. This covers lists, data extensions, groups, and filters. This works for Data Extensions when the Email is send via Email Studio -> Email -> Content -> Send flow. However, when Email is being sent from Journey Builder, _DataSourceName shows "All Subscribers" instead of the name of the Entry Data Extension. This is true for both Multi-Step Journeys and Single Email Sends. Default Email Address Settings (use email from Entry Source vs Contacts) also does not impact the outcome. _DataSourceName should show Entry Data Extension Name for Emails in Journey Builder, as it is very useful for:- debugging from Send Log- creating dynamic logic in emails based on Data Extension naming convention
_DataSourceName personalisation string, as per documentation, should show any audience object sent to. This covers lists, data extensions, groups, and filters.
This works for Data Extensions when the Email is send via Email Studio -> Email -> Content -> Send flow.
However, when Email is being sent from Journey Builder, _DataSourceName shows "All Subscribers" instead of the name of the Entry Data Extension.
This is true for both Multi-Step Journeys and Single Email Sends. Default Email Address Settings (use email from Entry Source vs Contacts) also does not impact the outcome.
_DataSourceName should show Entry Data Extension Name for Emails in Journey Builder, as it is very useful for:- debugging from Send Log- creating dynamic logic in emails based on Data Extension naming convention
Merge Idea · Flag
Zoe Polansky - 2 months ago
Help us to keep IdeaExchange clean by pointing out overlapping ideas. We'll investigate your suggestion and merge the ideas if it makes sense.
Thanks for your merge suggestion. We will review it shortly and merge the ideas if applicable.
Salesforce takes abuse situations very seriously. Examples of abuse include but are not limited to posting of offensive language or fraudulent statements. To help us process your request as quickly as possible, please fill out the form below describing the situation. For privacy and security reasons, the final outcome of an abuse case may not be revealed to the person who reported it.
Thank you for your feedback. We take abuse seriously and will investigate this issue and take appropriate action.