Summary Field Issue
I am at my wits end and have decided to reach out for help. This is the same project that I was previously posting for assistance with API calls. I moved on from using API's and have revamped the de...
Forum Discussion
MarkShnier__You
Qrew Legend
Qrew LegendSo if I have the story right, a member comes to a meet up but does multiple check-in's. The Issue is that they get charged for coming to the meet up and not for each check in.
So the only way to know how many meet ups an individual member went to is to have a table where the key field is a concatenation of the Related Member and the Related meet up. Table would be called Member Meet up Attendance.
I would set up the table with that key field as a text field and initialize it by running a summary report of all the check ins summarized by the field on the checkins table which is a formula text concatenation like
List("-", totext([related member]), totext([Related Meet up])
This would be a summary report. You would then copy that report over to the unique member meet ups table. That is just to do a one time initialization of the table.
Then on the Member meetups table you would put in a field called square [Member- Meetup Exists?] This will be a formula checkbox field set to the formula of
true
Then you would look that up down into checkins.
Then you were set up an automation so that when a checkin record is created and that look up field is equal to unchecked meaning that no member check and record yet exist in the automation would create one.
Then once you are that far you can either run reports off that member meet up table or you may just find it easier to flag check ins ends where the record id of the check in is equal to the Minimum Record ID of all check ins on the relationship where one member meeting has many checkins. In other words you will flag the first check in at a meet up as the one that you will charge four dollars for and ignore the rest on your reporting.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
So the only way to know how many meet ups an individual member went to is to have a table where the key field is a concatenation of the Related Member and the Related meet up. Table would be called Member Meet up Attendance.
I would set up the table with that key field as a text field and initialize it by running a summary report of all the check ins summarized by the field on the checkins table which is a formula text concatenation like
List("-", totext([related member]), totext([Related Meet up])
This would be a summary report. You would then copy that report over to the unique member meet ups table. That is just to do a one time initialization of the table.
Then on the Member meetups table you would put in a field called square [Member- Meetup Exists?] This will be a formula checkbox field set to the formula of
true
Then you would look that up down into checkins.
Then you were set up an automation so that when a checkin record is created and that look up field is equal to unchecked meaning that no member check and record yet exist in the automation would create one.
Then once you are that far you can either run reports off that member meet up table or you may just find it easier to flag check ins ends where the record id of the check in is equal to the Minimum Record ID of all check ins on the relationship where one member meeting has many checkins. In other words you will flag the first check in at a meet up as the one that you will charge four dollars for and ignore the rest on your reporting.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
- Thanks, Mark. I had my fingers crossed for something less involved. :p While reading through and thinking over your explanation, I came up with this question. When additional people need to be added for future check ins, will I have to have them added to the Membership table and update the Member Meetup Attendance table before the solution will work for them?
Can automation be setup to remove duplicate records (if any) once per day? The likely that multiple check ins by the same individual for the same meetup in the same day is extremely slim so, if this automation can occur (and be setup in a less complicated fashion), this might be a good alternate course of action until I get the other bells and whistles in place.
------------------------------
James Carr
------------------------------- MarkShnier__YouWell yes for this
When additional people need to be added for future check ins, will I have to have them added to the Membership table
I presume that in your credit app a member cannot do a checking unless they already exist as a member.
as for this
Can automation be setup to remove duplicate records (if any) once per day?
Are you asking to have a duplicate check in records deleted if so yes an automation can remove records which are duplicated where the same member has more than 1 check in for a member meeting record. The automation would retain all these a check in which had the Minimum Record ID for the check-ins related to the member meetings table and delete the rest.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------- You presume correctly, regarding a member not being able to check in unless they are on file. I just wanted to make sure I didn't miss anything with regards to adding additional people that can potentially check in.
As for the automation, that sounds good (and helpful to learn how to do). Is there documentation on it and/or some instructions you can provide? I have been searching and haven't found anything yet.
------------------------------
James Carr
------------------------------
