Back to Kinetic Platform Integrations
Handler · Version 1

Kinetic Reporting Database Upsert Kinetic Platform

GitHub

Configurations
Name Description Sample
api_server Kinetic Request CE API Web Application http://server:port/kinetic
api_username Name of user account that has permission to use the API
api_password Password for the API user *********
space_slug Slug of the Space where the User will be created.
jdbc_database_id The JDBC Id from the connection string for the database being used. ie. (oracle, sqlserver, postgresql, mysql). sqlserver
jdbc_url_opts Additional JDBC URL connection string options, such as ssl=true&sslmode=verify-full for Postgres.
host IP address or hostname of the SQL reporting database server.
port Port number the SQL server is listening on.
database_name SQL database name used for storing CE submissions.
database_identifier_size Max database identifier size. Not required to set for MSSQL, Oracle or PostgreSQL. Default for MSSQL is 128, Oracle 30, and PostgreSQL is 64.
user Username used to authenticate to the SQL server. Must have table creation and modification rights.
password Password for the SQL user account. *********
enable_debug_logging Enable debug logging if the value is set to 'Yes'. No
Parameters
Name Description Sample
Error Handling Determine what to return if an error is encountered.
Space slug (info value override)
Updated at start time (ISO8601)
Updated at end time (ISO8601)
Submission page size
Task deferral token
Kapp slug (optional for narrow scope) Kapp slug. Required if specifying specific form slugs to retrieve submissions from.
Form slugs (optional CSV for narrow scope) Form slugs (comma separated). Required if specifying specific form slugs to retrieve submissions from along with Kapp Slug parameter.
Skip writing Datastore submissions to kapp form Should writing datastore records to a common kapp form in the SQL database be ignored (submissons are still written to their own table)?
Results
Name Description
Submission Database Id
Handler Error Message
Changelog

Kinetic Reporting DB Upsert V1 (2021-06-12)

  • Initial version. See README for details.

Update - v6 fieldKey hotfix (2024-12-10)

  • Hotfix added to increase fieldKey column size to accommodate for GUIDs in v6 being the default entry of the field

Kinetic Reporting DB Upsert V1.1 (2025-07-24)

  • Updated to rework 1000 record limitation issues. New strategy uses recursive searching using the updateAt values
  • Updated to support datastores as a regular Kapp, vs a "special kapp"
    • Table naming had previously been app_, and no common kapp-table was written for legacy Datastore forms
    • Added a new run-time input to support NOT writing submissions to a common kapp-table for a kapp-slug named 'datastore'
  • Added support for kapp-defined fields for each kapp
  • Corrected the page_size logic to properly use page-size inputs from the run-time hander parameters
  • Updated processing to handle situations where new fields have been added to a form; previously this required restarting the Task / Agent server where this handler was running
Download GitHub

On This Page

Looking for a workflow engine? Learn more about the Kinetic Data Enterprise Workflow Platform. Check it out
Return to Top