Forum Discussion
It's not clear to me what you are hoping to achieve, but likely you'd want some record to contain a User or email value. Then, you'd include that field in a single Pipeline. The email address would then vary as necessary on the given record and feed dynamically into the Pipeline.
Or put another way, suppose you had hundreds of Users in your App … you *wouldn't* want hundreds of nearly identical Pipelines (one Pipeline for each User). Instead, just feed a common Pipeline the dynamic data. I'd imagine the triggering event defined in "Step A" of your Pipeline you'd specify a User or email address in the "Fields for Subsequent Steps."
Oftentimes, we'll create a formula field on a given table to display a given User email for debugging and using in reports. For example,
// Formula - Email Field Type
UserToEmail([Your User Field])
Hopefully that helps or gives you some ideas!
------------------------------
Brian Seymour
------------------------------
- JessicaMatenga2 years agoQrew Trainee
Hi Brian
Thank you for your response. It would more likely be max 10 x users requiring to email directly out of QB. If I create the formula email field type, how does the pipeline know which of the outlook accounts to use. In Step A I have added to the Query the Record Owner > Email see image below
the email address for the user
Each user will still have its own pipeline but I was wondering if this is too clunky for the system or is there an easier way.
------------------------------
Jessica Matenga
------------------------------- MarkShnier__You2 years agoQrew Legend
Jessica, because you need to make that "Connection" to the Outlook I'm fairly sure that you need separate Pipelines per user.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------- JessicaMatenga2 years agoQrew Trainee
Thanks Mark, yes you are correct and I am in the process of setting up each pipeline. Just wondering if my set up was the best way and also because one user has 2 x email addresses, other than him having to log in as a separate user (as my query is based on the record owner email), is there a better method?
Thank you
------------------------------
Jessica Matenga
------------------------------