Skip to main content
Question

Sending a weekly report of confirmed reservations to non-quickbase registered emails

  • February 9, 2023
  • 0 replies
  • 42 views

Every week, we need to send a report of confirmed reservations for the upcoming week to the relevant park manager. We have a lot of park managers.

I have already created a report that shows all confirmed reservation records for the next ten days, which is then filtered further by park/superintendent.

The real issue here is figuring out an easy way to click a button and send that report (since non user emails are not allowed as recipients in notification subscriptions) to all relevant emails. Further, the report looks like this: 

When the non-user recipient receives this open email notification, they can look at this report, but they lack the permissions to be able to view the records linked within this report (by clicking on one of the underlined numbers). Is there a way to, instead of sending this whole report to non users who are then unable to view the records linked within, send the actual records themselves that this report filters for, but in an automated way? Can't afford to add all managers/supers/recipients to paid quickbase seats.

This is what the actual reservation record looks like when drilled-down-to from the above report:

I notice that it's possible to manually send the individual record via email (so that the non registered recipient can see the information), but I would prefer that our reservationist doesn't have to manually drill down on every confirmed reservation and then type out the emails that said record needs to be sent to. 

I know this is a lot, but this is the absolute last piece of this to-be-deployed reservation system that needs finishing. Any assistance would be greatly appreciated.

Thank you,



------------------------------
Coleman DuCharme
------------------------------
This topic has been closed for replies.

  • Author
  • Quickbase Alumni
  • February 9, 2023

I should add, they lack the permission to be able to drill down into records from the "upcoming confirmed reservations" report - because EOTI submits "new reservation requests" to the same table that the report drills down into (to view individual confirmed records). We don't want all of our park constituents who submit reservation requests (functionally, "EOTI") to be able to look at reservation records that others have submitted. Which in turn makes it so that the non registered email recipients of the "upcoming reservation report" (also functionally "EOTI") cannot drill down into and view individual records linked on the emailed report. 



------------------------------
Coleman DuCharme
------------------------------