• Home
  • Custom Programming

Programming TouchPoint Using Python and SQL

Programming TouchPoint Using Python and SQL

This is your guide to how you can use Python and SQL to make TouchPoint sing to your own tune.

Custom Recipes

A great way to learn programming TouchPoint is to use some of our custom recipes for examples of what you can do.

Below are what we call recipes for both Python and SQL Reports. These are step-by-step instructions, complete with the code you can copy and paste into your database. This makes it easy for someone who is not proficient in these programming languages to create these specific reports.

Both SQL and Python reports have the option of being added to either the main Reports menu or to the Blue Toolbar. After running the report, there will be a link at the bottom. It is Add Report to Menu. If the report is suited for the Blue Toolbar, the recipe will contain the code necessary to place it there, should you choose to add it to the menu.

Without that code, the report will appear on the main Reports menu, when you choose the option to add to menu.

Reports that are suited for the Blue Toolbar are those that depend on a set of individuals, such as an organization, a Tag, or Search Builder results. Other reports should appear on the Reports menu, because they are more global in scope.

Writing Your Own Scripts

We prefer that you develop your SQL scripts on a local copy of your database before you install them in your production database. That is what we do so that we can perfect the code and know that it does not have errors and is performant. When you develop and test in your production database, we see every error messages every time you make a mistake and it could cause performance problems for other churches if you write an untested script that hogs resources unnecessarily. And even though there is no danger of damaging anything since you will have read-only permissions through SQL on the production database, you can hog resources since you share a database server with all of our other churches.

Your database is housed on a Microsoft SQL Server 2016 database. You can get a free Express version of this database system from Microsoft. See the links at https://github.com/bvcms/bvcms/blob/master/README.md under Developer tools.

We can make arrangements for you to download the nightly backups of your church’s database. You just need to setup your own Rackspace cloud files account and then provide us with the access token from Rackspace. Then we add your database backup to that account every night. From here you will be able to see the database schema.


We charge a one-time setup fee of $50 to script the backups to your account. The Rackspace cloud files account will be very inexpensive, probably less than $5 a month, even less if you keep old files cleaned out regularly.

Latest Update 12/10/2020

Removed directions for downloading open source code.