Select your data file (the CSV you just created from Salesforce), and click Next. I like the address label without a barcode. The default label is Address Barcode on Top, but you can change this if you like. In the Dymo Label app on your computer, use File->Import Data->New. Then do an Export, and choose “Details Only” with format CSV. In my case, that would be the Status field. Once you have all your fields selected, use filters to reduce the list to only the contacts you want, selecting on the field you used to determine if the contact gets a card. If required, you can also add Mailing Country.
#Salesforce mass mailings update
Select “Accounts & Contacts,” and use the report type “Contacts & Accounts.” Update the columns so you use the following fields: In Salesforce, go to Reports->New Report.
#Salesforce mass mailings how to
(If you’re unsure how to add a new field to an object, watch this video from Salesforce.) I have a Status field that allows me to find customers who have a Support agreement with me, and I select on that basis. You may want to create a new field in your Contacts account that allows you to mark customers who should receive cards. Though ultimately its only dictating how many instances of each you pass in the array to the send email, which ultimately then governs overall what can be sent anyway.Thanksgiving and Christmas are just around the corner – would you like to send cards to your customers? Doing this with Salesforce and a Dymo printer is quite straightforward. If you scaling above my earlier example of 50 and working with these objects, this is indeed an additional benefit to those I've described above. As you say there are quite a few more features on the SingleEMailMessage, but if you don't need any of those perhaps the MassEmailMessage has a place. So there is arguably a marginal heap and statement benefit as well. Instead of creating 50 SingleEmailMessage instances each setup accordingly (you'll have to pull the email addresses yourself) to achieve the same. So if you had 50 such Contacts to email you need only have a single MassEmailMessage instance and set a list of those Id's into it. What MassEmailMessage appears to give you is a more optimal coding route if you are focusing on sending to Contacts, Leads or Users relating to either Contract, Case, Opportunity or Product objects.
So what am I missing? What's the advantage of using a MassEmailMessage for sending out a batch of emails when the SingleEmailMessages have more options? Single and Mass emails have separate limits, but they both have the same limit of 1,000 external email addresses per day.Īnd when it comes to using the ndEmail(), you have pass in an array of messages anyway, so why not send in an array of many Singles instead of an array of one Mass? Mass emails have very limited options for the setWhatIds. If you look at the documentation, Singles have far more options available when it comes object types that can be used in the setWhatId methods, especially since they can accept Custom objects. I'm scoping out a project that will involve sending outbound email messages, and I'm a little confused about why one would use a MassEmailMessage instead of multiple SingleEmailMessages.
0 kommentar(er)
