Lookup Specification: Difference between revisions
Dgreenwood (talk | contribs) No edit summary |
Dgreenwood (talk | contribs) |
||
| Line 6: | Line 6: | ||
* [[Database Lookup]] | * [[Database Lookup]] | ||
* [[CMIS Lookup]] | |||
* [[Lexicon Lookup]] (uncommon) | * [[Lexicon Lookup]] (uncommon) | ||
* [[Web Service Lookup]] | * [[Web Service Lookup]] | ||
* [[XML Lookup]] | * [[XML Lookup]] | ||
Revision as of 14:39, 5 September 2025
|
STUB |
This article is a stub. It contains minimal information on the topic and should be expanded. |
A Lookup Specification defines a "lookup operation", where existing Grooper fields (called "lookup fields") are used to query an external data source, such as a database. The results of the lookup can be used to validate or populate field values (called "target fields") in Grooper. Lookup Specifications are created on "container elements" (data_table Data Models, insert_page_break Data Sections and table Data Tables) using their Lookups property. Lookups may query using all single-instance fields relative to the container element (including those defined on parent elements up to the root Data Model), but cannot be used to populate a field value on a parent of the container element.