Action If Record Already Exists
I have a Meetups table and a Check Ins table related to each other, where the Meetups is the parent table. I am looking to add the following functionality: 1) If the Check Ins record does not exi...
Forum Discussion
Update: I have managed to get results using API_DoQuery and, from what it looks like, API_DoQueryCount. My dilemma, though, is I am getting a link that is taking me to an XML page. I don't know how to capture the resulting count from API_DoQueryCount in my Formula Url field. The next step, of course, would be to Save and Send a notification or just simply send a notification depending on whether or not that value is greater than 0. I am still open to taking a completely different direction from using the API_DoQueryCount call, if someone has a viable suggestion for me. I will keep digging and will advise if I get any more results before someone else helps me produce a solution. Thanks, again (and in advance), for any assistance.
------------------------------
James Carr
------------------------------
------------------------------
James Carr
------------------------------
- MarkShnier__You
Qrew Legend
I am not understanding your desired workflow. Are you saying that the user is entering a check in record which may or may not be duplicate? Is that the beginning of this process? For now leave aside all the technical stuff and it just explain your workflow.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------- Sorry. I have to remember that I have to approach my questions differently. Here's the situation:
Member adds a Check In -> Check In does not already exist -> record is added and a notification is sent to the Member with details for accessing the virtual class
Member comes back (for whatever reason) to Check In again because he/she needs the details again so....
Member adds a Check In -> Check In already exists -> another record is NOT added; a notification is sent to the Member with details for accessing the virtual class
------------------------------
James Carr
------------------------------- MarkShnier__You
At EMPOWER they demoed you're approach. But that as just directional and won't be coming for a year.
so what we do Quick Base style is to create a Parent Record in a new table called Member Meetings. Set the key field to be hyphen delimited concatenation of the Record ID of the Meeting and the Member.
Make afield there called
Member Meeting Exists? With a formula if true
make a relationship back down to check in's with calculated reference field
Look up that check box field and now you know if there is a parent.
maintain the master table with an Automation
initialize the master table off a summary report from checking
So yes quite a few steps and if you know what you're doing you can do it in about five minutes but at least you can know that QuickBase recognizes that it would be nice to do this without having to create a relationship and look up fields to make this happen
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
