- Release notes
- Getting started
- Installation
- Configuration
- Integrations
- Authentication
- Working with Apps and Discovery Accelerators
- AppOne menus and dashboards
- AppOne setup
- TemplateOne 1.0.0 menus and dashboards
- TemplateOne 1.0.0 setup
- TemplateOne menus and fashboards
- TemplateOne 2021.4.0 setup
- Purchase to Pay Discovery Accelerator menus and dashboards
- Purchase to Pay Discovery Accelerator Setup
- Order to Cash Discovery Accelerator menus and dashboards
- Order to Cash Discovery Accelerator Setup
- Basic Connector for AppOne
- SAP Connectors
- Introduction to SAP Connector
- SAP input
- Checking the data in the SAP Connector
- Adding process specific tags to the SAP Connector for AppOne
- Adding process specific Due dates to the SAP Connector for AppOne
- Adding automation estimates to the SAP Connector for AppOne
- Adding attributes to the SAP Connector for AppOne
- Adding activities to the SAP Connector for AppOne
- Adding entities to the SAP Connector for AppOne
- SAP Order to Cash Connector for AppOne
- SAP Purchase to Pay Connector for AppOne
- SAP Connector for Purchase to Pay Discovery Accelerator
- SAP Connector for Order-to-Cash Discovery Accelerator
- Superadmin
- Dashboards and charts
- Tables and table items
- Application integrity
- How to ....
- Working with SQL connectors
- Introduction to SQL connectors
- Setting up a SQL connector
- CData Sync extractions
- Running a SQL connector
- Editing transformations
- Releasing a SQL Connector
- Scheduling data extraction
- Structure of transformations
- Using SQL connectors for released apps
- Generating a cache with scripts
- Setting up a local test environment
- Separate development and production environments
- Useful resources
Lookup expressions
Lookup expressions have some similar elements as Aggregate expressions but also have some new elements. Lookup expressions can be seen as an implicit join with an input table. A Lookup expression enables you to access all attributes from the selected input table.
Follow these steps to create a Lookup.
Step |
Action |
---|---|
1 |
Create a new expression. |
2 |
Change its Type to Lookup and select the desired input table. |
3 |
Set the expression level as needed. |
4 |
Right-click in the lookup column, next to the Settings column, and select Add attributes… to add a lookup attribute. |
5 |
Enter the lookup expression in the Expression field. |
6 |
Click on OK to save the Lookup expression. |
If you want to use an attribute in a table that is not available in that table, you can create a lookup to a table in which the attribute is available. You create the lookup by using an attribute that is available in both the current table as the input table.
If you want to use the Invoice owner in the Events table, you must create a lookup to the Invoice table since the attribute is only available in the Invoices table. To get the information to the Events table, a lookup is created. To find the proper Invoice owner per event, the Invoice number which is available in both tables is used.
See the illustration below.
This expression adds a Lookup expression attribute to the Events table which stores the Invoice owner of each event.
Invoice number
is added in both columns since it is the shared key between the Lookup table and the Input table.
All attributes listed above the expression level must be included in the Lookup column since they are needed to join both tables. Attributes below the expression level do not need to be shared by both tables.
Any attribute from the Input table can be placed in the Settings column below the expression level, in case it is needed for the lookup definition. In the example below, the Event end attribute is used to sort the records.
Case_preprocessing
table that counts the distinct number of people who work on an invoice.
Lookups can also be used in the Globals table to get information from other tables that can be aggregated in one value. For example, to know whether an attribute is filled. See the illustration below for an example.
In this Lookup expression it is checked whether the Event end attribute has a value or not. No shared attributes are needed since all records of the table are accessed to handle them all together.