2023:Data Connection (Node Type)
|
This article is about an older version of Grooper. Information may be out of date and UI elements may have changed. | |
| 2025 | 2023 |
|
STUB |
This article is a stub. It contains minimal information on the topic and should be expanded. |
database Data Connections connect Grooper to Microsoft SQL and supported ODBC databases. Once configured, Data Connections can be used to export data extracted from a document to a database, perform database lookups to validate data Grooper collects and other actions related to database management systems (DBMS).
- Grooper supports MS SQL Server connectivity with the "SQL Server" connection method.
- Grooper supports Oracle, PostgreSQL, Db2, and MySQL connectivity with the "ODBC" connection method.
Grooper can connect to a Microsoft SQL Server or ODBC-compliant providers (such as Oracle, Db2, MySQL and PostgreSQL).
Data Connections are primarily used for two reasons in Grooper
- To validate data extracted from a document or to populate fields using values stored in a database.
- This is done using Database Lookups defined on Data Models.
- To export collected data to a database.
- This is done using Data Exports defined using Export Behaviors
Glossary
Data Connection: database Data Connections connect Grooper to Microsoft SQL and supported ODBC databases. Once configured, Data Connections can be used to export data extracted from a document to a database, perform database lookups to validate data Grooper collects and other actions related to database management systems (DBMS).
- Grooper supports MS SQL Server connectivity with the "SQL Server" connection method.
- Grooper supports Oracle, PostgreSQL, Db2, and MySQL connectivity with the "ODBC" connection method.
Data Export: Data Export is an Export Definition available when configuring an Export Behavior. It exports extracted document data over a database Data Connection, allowing users to export data to a Microsoft SQL Server or ODBC compliant database.
Data Model: data_table Data Models are leveraged during the Extract activity to collect data from documents (folder Batch Folders). Data Models are the root of a Data Element hierarchy. The Data Model and its child Data Elements define a schema for data present on a document. The Data Model's configuration (and its child Data Elements' configuration) define data extraction logic and settings for how data is reviewed in a Data Viewer.
Database Lookup: Database Lookup is a Lookup Specification that performs a lookup against a database Data Connection via a SQL query.
Export Behavior: An Export Behavior defines the parameters for exporting classified folder Batch Folder content from Grooper to other systems. This includes where they are exported to (what content management system, file system, database etc), what content is exported (attached files, images, and/or data), how it is formatted (PDF, CSV, XML etc), folder pathing, file naming and data mappings (for Data Export and CMIS Export).
Export: output Export is an Activity that transfers documents and extracted information to external file systems and content management systems, completing the data processing workflow.
Project: package_2 Projects are the primary containers for configuration nodes within Grooper. The Project is where various processing objects such as stacks Content Models, settings Batch Processes, profile objects are stored. This makes resources easier to manage, easier to save, and simplifies how node references are made in a Grooper Repository.
How To
Create a Data Connection
Data Connections can be created in any Grooper Project. 2023:Database Lookup
Use a Data Connection for Database Lookups
Coming soon
Use a Data Connection for Data Export
Coming soon
Known Issues
The Grooper installer ships with various prerequisite components which are installed before the Grooper application. This includes CLR type mappings for various SQL data types. Without additional components installed, users may experience the following error when attempting to preview database tables with unsupported CLR Types (such as geometry and geography data types):
InvalidOperationException: DataReader.GetFieldType(24) returned null.
To support additional CLR Types (including geometry and geography data types), users need to install the following prerequisite from Microsoft: