Forum Discussion
AustinK
5 years agoQrew Commander
I have also been looking into this over the past few weeks. This isn't exactly what you want but you may be able to adapt it. I am considering doing the same.
https://community.quickbase.com/blogs/brian-cafferelli1/2020/06/01/how-can-i-email-a-report
At the bottom of this this is one big caveat that I will copy over to here.
Reports emailed by pipelines however, are static. This means that all recipients will receive the same version of the emailed report. Therefore, take care that all contents of reports emailed through pipelines are appropriate to share with all recipients of that email. Pipelines run using the permissions of the app builder who created the pipeline.
https://community.quickbase.com/blogs/brian-cafferelli1/2020/06/01/how-can-i-email-a-report
At the bottom of this this is one big caveat that I will copy over to here.
Reports emailed by pipelines however, are static. This means that all recipients will receive the same version of the emailed report. Therefore, take care that all contents of reports emailed through pipelines are appropriate to share with all recipients of that email. Pipelines run using the permissions of the app builder who created the pipeline.
DavidMinker
5 years agoQrew Trainee
Thanks to you both for the input / feedback.
What I ended up doing was creating my own version of the report in Pipelines with a combination of the QB and Mailgun channels and used some Jinja + Markdown to build, essentially, the same report I was triggering via the Scheduled Reports.
I'm relatively certain this same solution will not be viable for future cases where I do need a variable (non-static) report based on recipient ... but at least I can move this ball forward.
------------------------------
Dave Minker
------------------------------