Difference between revisions of "Codeunit/Integration/IntegrationFieldLookupKey"
Jump to navigation
Jump to search
old>Admin |
m (5 revisions imported) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 17: | Line 17: | ||
[fieldmapping] > Configuration values | [fieldmapping] > Configuration values | ||
Example: | |||
SELECT Name FROM user WHERE Email = '@VALUE@'; | |||
The expression must contain the parameter: '''@VALUE@''' | The expression must contain the parameter: '''@VALUE@''' | ||
== Developer info == | == Developer info == | ||
* Type: CodeunitTranslator | * Type: CodeunitTranslator | ||
* Security: None | * Security: None | ||
Latest revision as of 11:51, 10 December 2021
What it does
Looks up another value based on the string provided, for use in a scheduled integration.
A lookup will be executed sustituting the @VALUE@ in the SQL expression passed to the codeunit.
Note that the @VALUE@ is SQL escaped for security reasons.
How to invoke
Insert value in field mapping Designer > Integration > Import sources > [intergration] > [fieldmapping] > Codeunit handler
dk.p2e.blanket.codeunit.common.IntegrationFieldLookupKey
Configuration
Insert an SQL expression in:
[fieldmapping] > Configuration values
Example:
SELECT Name FROM user WHERE Email = '@VALUE@';
The expression must contain the parameter: @VALUE@
Developer info
- Type: CodeunitTranslator
- Security: None