@Aleksi_Alkio Here’s the solution I came up with to mass email people in a table or slice. I combined both of your suggestions. I thought I’d lay it all out in case someone else searching this community ever has the same issue.
This is for an app that manages a choir sheet music library and a large choir; along with the directors, chairmen, pianists, etc of the smaller choirs that come together to make the large choir. I created an additional table (EMAIL MESSAGES) with these columns:
[From:]-- Enum with my 3 users’ names,
[From Email:]-- Enum
[To:]-- Enum of 2 different groups of people we email regularly (“Stake Choir Members”, or the “Directors and Presidents” of each of the 8 smaller choirs) [Subject:] – text [Body Paragraph 1:], – longtext [Body Paragraph 2:],-- (optional) longtext
[Salutation:]-- Enum (Thank you, See you there, Until next time, etc.) [Date/To] – virtual column, and my “key”: =CONCATENATE([Date:],[To:])
Then, I created a workflow in the behavior section to trigger an email:
Target data: the EMAIL MESSAGES table.
Updates on: “ADDS_ONLY”.
Condition: = AND(AND(ISNOTBLANK([Date/To]),[_THISROW_BEFORE].[Date/To]<>[_THISROW_AFTER].[Date/To]),([To:]=“Stake Choir Members”)) That expression triggers the email every time “Date/To” is filled out AND the email is [To:] the choir members. Send to: =[From Email:] so I can BCC the real recipients Subject: <Subject:> Email Body: I’ll get back to this after explaining the next parts. CC: the email addresses of the bosses of the organization BCC: =Choir Roster[Email Address]
“Choir Roster” is a table in my app Reply to: =[From Email:] Pre-header: I changed the auto-generated expression a bit. <<Body Paragraph 1:>> by ‘<<USEREMAIL()>>’ at <<NOW()>> Email body template: I clicked “create”, then waited for it to generate a DocId= number and clicked “view”. It takes you to a google doc with all your column fields and their labels. I deleted all except the parts I wanted to show up in the email. That template now looks something like this:
<<Body Paragraph 1:>>
<<Body Paragraph 2:>>
Then I went back up to the “Email Body” section and pasted that same DocId number, so the body of the email generates according to the template I just created.
I then duplicated the whole workflow rule (to account for the other group of people I email) and changed the condition expression to include “Choir Directors and Presidents” instead of the choir members.
THEN, in the UI/UX area, I added a form view to my menu of that EMAIL MESSAGES table.
So, now when I go to my menu, I click on the “Email” option, and I’m taken to a form. I fill it out (most of which is Enum drop down menu except the subject and body paragraphs), and click save. 10 seconds later, there’s an email in my inbox.
Sorry. I’m excited. And my brain hurts.