- Calculated Property
- Google Sheets
SQLiteLast Updated: 2022-01-14
Grouparoo's SQLite Integration is both a Source and a Destination that enables you to import and export customer data to and from one or more SQLite databases. SQLite is a relational database management system (RDBMS). You can use Grouparoo to sync data between a SQLite database and other services to operationalize your data.
|SQLite Import Table||Import or update Records from a SQLite database table.|
|SQLite Import Query||Import or update Records via a custom SQLite query.|
|SQLite Export Record||Export Records to a SQLite table. Groups will be exported to a secondary table linked by a foreign key.|
To work with the SQLite Plugin, you must first install it in an existing Grouparoo project. Grouparoo supports syncing with SQLite databases stored on a local machine. Part of configuring the App will be to supply the database file location to establish the connection between Grouparoo and SQLite, so you will also need a path for the local database to refer to as part of configuration.
To connect SQLite to Grouparoo, you create an App to tell Grouparoo how to connect to SQLite. This specifies the location of the database you want to sync data to or from.
In Grouparoo, you specify the options to connect to SQLite.
|File (required)||This should be the Absolute path of the SQLite database file you want to use in syncing data.|
This source reads from a single table in your SQLite database using a primary or foreign key. Properties are generated from this table from row values or aggregations of row values.
There is one option to set for a SQLite Table Import Source. You need to choose a table from the database to serve as the location for Grouparoo to scan for changes to Properties.
|Table (required)||The table you want to scan for updates to your data.|
Defining Mappings is a critical part of the process. It tells Grouparoo which Record to associate with the imported data.
If you are using SQLite Import Table as the primary source, choose the SQLite column that uniquely identifies Records in your Model. This will often be the primary key of the table that represents your Model.
In secondary sources, choose the SQLite column that ties this table to your primary source. This will often be a foreign key in your table.
Create a schedule to actively pull new data from this SQLite table. If the recurring option is not selected, you are creating a one-time sync. There are also options to confirm records exist when running a schedule and to enable refresh.
Configure a schedule for your project and determine how Grouparoo should check for new data by selecting filling out the options for this Source.
|column (required)||Select which column Grouparoo should check to look for new data. Often, this would be a column like “updated_at” - Grouparoo remembers the most recent values so it can be based on an incremental count as well.|
If there is a subset of rows data you want to specifically include or exclude from your SQLite table, create a filter.
Properties populate your Records with data from your SQLite table based on table columns. Create a Property to be able to use row data in Grouparoo.
|Column Name (required)||Choose the column that will be the source of data for this Grouparoo Property.|
|Aggregation Method (required)||Aggregation methods determine how to use the row values in the table. SQLite supports the standard set of aggregation methods for table sources.|
If there is a subset of data for a specific primary or foreign key you want to include from your SQLite table, create a filter.
A Query Source works differently than a table-based source in that there are no any options to choose in setting up the connection to this type of source. A Query Source is a more flexible way to build properties.
This type of Source provides the ability to write custom SQL code to extract data from one or more tables and import the result into Grouparoo.
A Destination’s sync mode determines what to update in a Destination. The following are supported by SQLite:
- Sync: Add, update, and remove SQLite Exported Properties as needed.This option looks for new records, changes to existing records, and deletions.
- Additive: Add and update SQLite Exported Properties as needed, but do not remove anybody. This option looks for new Records to add to SQLite and changes to existing SQLite Records, but does not keep track of deletions.
- Enrich: Only update those Properties that already exist in SQLite. Do not add or remove Properties. This option will only update existing Properties in the SQLite database.
To further clarify how SQLite should sync data, select from the options provided that are specific to your database.
|Table (Required)||The name of the table used to export Records. You must choose a table that already exists in the SQLite database you are syncing to.|
|Primary Key (Required)||The primary key of the table. This will be used in the mapping of properties.|
|Groups Table (Required)||The name of the table used to export groups. This table must already exist in your database and must use a foreign key to relate to the primary key you have already designated for in the previous field.|
|Group Foreign Key (Required)||The column name for the foreign key that the groups table uses to reference the records table.|
|Group Column Name (Required)||The column name used to store group names.|
In an SQLite Export Record Destination, you must choose the Grouparoo Property to map to the column listed as the primary key in the SQLite database table this Destination will sync to. Therefore, the Exported property listed as required will be whatever is designated as the Primary Key in the SQLite table.
In addition to the required mapping for your table’s primary key, any other columns in the table can also have mappings to Grouparoo properties.
In addition to mapping Grouparoo Properties to SQLite Properties, you can use Grouparoo Groups to assign records to a Group in SQLite. This information is recorded in a table that lists the Grouping alongside a foreign key that relates to the associated Record being assigned to that Group in the SQLite database.
We strive to keep our documentation accurate, easy to use, and up to date. If you notice that something has changed or is not addressed in the process of setting up your Grouparoo connection with
SQLite, please let us know by reaching out to email@example.com.
As always, if you need support using Grouparoo, reach out to community members in our Slack channel. We are always happy to help!Join us on Slack
- Calculated Property
- Google Sheets