Good day,
I’ll admit I only took a quick stab at this; I sense that within the Expression editor the “@” values are validated and resolved to their respective internal ID – not complied with each run through. I figured it couldn’t’ hurt to ask.
Summary
I was hoping to construct a @TableRecord reference, within a trigger expression – made up of the value from another table record or variable.
For Example, we may have an Orders table record loaded that has numerous fields we want to use the data from.
@Table Record.Orders.
I have another Table record that contains the particular column/field within the Orders record that I need to leverage – it is different for each product. (Part of a step loop creating a JSON payload)
For Example:
@Table Record.NeededPayload.Field
Contains the value : Item
Next run through the loop
@Table Record.NeededPayload.Field
Contains the value : PO
Currently I have each possible Field value defined as a condition – with an expression with then a statically declared table record value for the Orders
IF field value = Item Then
@Table Record.Orders.Item
IF field value = PO then
@Table Record.Orders.PO … etc
These may be just picking up the value, or they may be part of a transformation of some sort.
I would like to be able to just have a single expression to handle all of the similar patterns (just handling one on each pass of the loop). So something like this
IF Any
@Table Record.NeededPayload.Field = Item
@Table Record.NeededPayload.Field = PO
Then Data Manipulation
Store Expression LINK((‘@Table Record.Orders.’+@Table Record.NeededPayload.Field)),’’)
Store To the Variable I’m using.
I do get a concatenation – but the value is just the concatenated string, not the value from the Orders table record – ex just ‘@Table Record.Orders.Item’
Any thoughts or input would be appreciated.
Thanks!
Chris