In the past, we had set an email address against a lookup item, I would enter the email address as a scoring value for those data items (e.g. a particular department name might have a specific inbox for candidate queries that can be used to automatically populate an advert for a quick ‘contact us’ for example).
For example, opportunity item with an ID of 58881 that is ‘Department’ could have a scoring value of oleeojobs@hello.com and then on an advert, you could enter [path]opportunity.formdata.58881:1:1.scoring_value[/path] (so the end is scoring_value rather than just value).
Instead, Oleeo support suggested we use the translation option instead (all credit to Julia for this!):
- On details page of a lookup list, tick any ‘Enable translation to’ option
- Then Export lookup values and open the downloaded spreadsheet
- The document will contain two tabs, values and translations
- Under the empty column, add the email address(es) as required
- Save the spreadsheet and ‘Import lookup values’
- The column heading contains a number - this is to be used when editing the datapath to be used which instead of scoring_value or value, will be translated_to.X.value
- E.g. [path]application.opportunity.formdata.14281:1:1.translated_to.4.value[/path] - X is 4
Hope that helps.
