The weeks fly by so fast. It seems like we just completed last week’s tutorial about emailing a queue overdue persons report. This week’s tutorial will build and extend upon last week’s tutorial. We focus on saving the data to a Excel/CSV file, and emailing the file as an email attachment. It goes without saying,
Category: CSV
I’m back with a doozy of a tutorial today based upon using Church Community Builder’s (CCB) API to create an overdue persons report. In short, CCB innately provides notifications when individuals are placed in a queue and their due date expires without the queue manager taking action. For example, our church has a number of
Using the CCB API to add individuals to queues and more…
I happened to check my email folder containing The Village’s emails, and found an email where someone was in need of a mass addition to process queues using the CCB API. Of course, you know this made me perk up a bit. I opened the email to find the need addressed as follows: In our
Automating the use of Processes, Queues, and Attendance Reporting
Geez, just re-reading the title makes me (and probably you too!) cringe at the thought of using the Church Community Builder API to automate processes, queues and attendance reporting into a repeatable dynamic action. That’s a thought and mouthful to repeat. Well, it’s been a fast moving week for me, and I’ve been a bit slow
Welcome back. It seems like weeks and days just fly by until the next tutorial. Last week, I covered how to access data that does not have a formalized api service. In that tutorial, we desired to access the “How They Heard” about us information for each CCB profile. I discussed the options of using
