Forum Discussion
EvanMartinez
Qrew Elite
Hi Michelle,
Basing a subscription off a report that filters by current user having records is something I've done plenty of times in my own apps and helping with customer apps in the past to help send out the subscription only when the user has relevant records. In the past it usually only doesn't work when something makes that field and data unreliable in the app. What issues do you think the field has? Is it part of a relationship or based on a formula that could be having its values changed somewhere outside the table so you aren't able to track that change?
------------------------------
Evan Martinez
Community Marketing Manager
Quickbase
------------------------------
Basing a subscription off a report that filters by current user having records is something I've done plenty of times in my own apps and helping with customer apps in the past to help send out the subscription only when the user has relevant records. In the past it usually only doesn't work when something makes that field and data unreliable in the app. What issues do you think the field has? Is it part of a relationship or based on a formula that could be having its values changed somewhere outside the table so you aren't able to track that change?
------------------------------
Evan Martinez
Community Marketing Manager
Quickbase
------------------------------
MichelleWoolley
3 years agoQrew Member
Hi Evan,
Can you give me an example of how you would set up one subscription that will only send an email if the person that the email is going to has records? The current subscription we have is set up to go to all QB users to try to catch everyone, but some of the QB users don't have anything to do with this QB table (i.e. they don't have a company credit card) so filtering based on a field in the report is tricky. That is one of the problems with how we set it up currently because some of the people are not identified in the table at all and they got the notification because they did not get filtered out.
------------------------------
Michelle Woolley
------------------------------
Can you give me an example of how you would set up one subscription that will only send an email if the person that the email is going to has records? The current subscription we have is set up to go to all QB users to try to catch everyone, but some of the QB users don't have anything to do with this QB table (i.e. they don't have a company credit card) so filtering based on a field in the report is tricky. That is one of the problems with how we set it up currently because some of the people are not identified in the table at all and they got the notification because they did not get filtered out.
------------------------------
Michelle Woolley
------------------------------
- EvanMartinez3 years agoQrew EliteHi Michelle,
To get the set up you are looking for you would set up the report the subscription is based on to filter for the user field in your table that you are using to be equal to the current user. Then so long as that checkbox you mentioned is not checked to send the email when there is no records as long as they don't have a valid record to show up using your filters they wouldn't get an email even if it is set to go to everyone. I have done that with apps with 5 users and apps with 500 users where many users have nothing to do with the table the subscription is based on.
In your instance where you have a user getting that email are they the only user that shouldn't have gotten an email but did or are there other users who shouldn't have gotten an email based on your filters and did indeed get no email? For example it is going to all users and it correctly went to 20 users who did have records, correctly did not go to 20 users who had no records, but then went to a user who had no records? That would more indicate that there is something special about that case (for example is that user in a special role in your application that could effect how they view relationship data or formulas that could impact the way they see that report) or alternatively that one user had a record that was edited either on the parent or child level.
------------------------------
Evan Martinez
Community Marketing Manager
Quickbase
------------------------------- MichelleWoolley3 years agoQrew MemberHi Evan,
We have that type of filter currently set up (see below snip) but this is the first time we have tried to do this.
And some people without records correctly did not get the report (I know of at least two).
The people with records correctly got the report.
Some of the people that got the report that should not have are people that are not set up with a card number at all and have nothing to do with the table.
Some of the people that got the report that should not have are people that are set up in the table and have had past records but do not currently have any missing receipts.
What type of user field do you usually use?
------------------------------
Michelle Woolley
------------------------------- MichelleWoolley3 years agoQrew MemberQuickbase customer support helped us out and it turned out to be simply of matter of needing to delete the notification and set it up again. Otherwise, we were all good. Thanks.
------------------------------
Michelle Woolley
------------------------------