User role as recipients for email

When using the user roles I get this error.

So what's your question?

  1. Check your database column names and your query to find the error.
  2. I can't see what's causing this.
  3. I can't see what's supposed to generate the 'to' addresses.
  4. 'Test@Ignition' is not a valid email address. Try adding '.com'.
  5. Is the same as 3.
2 Likes

I never emailed based on roles before but 3 and 5 from what you pointed out - @jbb5310 are there any users with those roles that have an email associated with them? Maybe you have users with those roles but no emails for those users?

1 Like

I'm working with the OP on here. The schedule is set up (annoyingly changes per day), and the parameters are configured in Data. We've narrowed it down to the following errors. However, we're not able to address items 3, 4, or 5 (as called out by Transistor above). I'm assuming this built-in user roles function on the report module works in v7.9 (yes, I know). As you can see in the circled areas, everything seems to be verified. We've also played around with the ReplyTo User Source (#4) and still get the same error. The manual calls this out as Optional anyway.

We do e-mail reports from this server.

There are users with valid e-mails associated with this role. It's just the two of us until it's proven.

Has anyone been successful with using this function? We saw a similar posting referencing system.report.execute, but I'd much prefer to handle everything "locally" rather than trying to reference external scripts and such.
ref: Scheduled report with scripted parameters

Going through the code, it looks like the user source for your TO addresses was successfully contacted but no users were found with that role. You might double check with a script (copy and paste the role name to be sure) that you are able to pull the roles, because the report sure isn't seeing users with that role and a contact type of email.

For the reply-to, well that role is blank, so that error is easy to solve. I suspect that may solve the last error as well.

1 Like