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. |
Data Connections are required to connect a Grooper Repository to an external database. The Data Connection stores all information needed to access the database. Once connected, Grooper has both read and write access to tables in the database (assuming you have those user rights in the database).
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
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: