Integration Map Reverse Lookup Fails When a Value Has No Mapping
What does "evaluating expression :org.mvel.ExecutableAccessor@211815af" mean in Workday Studio?
An integration map lookup found no match for the value it was given and returned an empty result, and the expression then tried to read the first item out of that empty result. It is reported as an unresolved property because the whole chained expression failed to evaluate, which makes it look misleadingly like the lookup function itself is missing.
Quick fix
Assign the lookup result to a property on its own line, then guard the item access so it only runs when that property is not empty, falling back to a default or omitting the field when it is.
Permanent fix
Never chain item access directly onto a map lookup. Always capture the result, test it for emptiness, and supply an explicit fallback, so an unmapped value produces a defined outcome instead of aborting the run. Keep a report of values present in the source data but absent from the map and review it whenever the source system adds new codes.
Troubleshooting
- Read the failing expression rather than the property name. What actually failed is usually the item access or the string conversion chained onto the lookup, not the lookup call itself.
- Identify the exact value being passed in and check whether it has a row in the map. A trailing space or a difference in case is enough to miss a mapping that looks present.
- Confirm you are calling the right direction. One direction takes the internal value and returns the external one, the other does the reverse, and calling the wrong one silently finds nothing.
- Decide whether a missing mapping should actually be fatal for this field. For an optional field it should not be, and the expression needs to tolerate the gap.
- Split the expression in two, assigning the lookup result to its own property first, so you can test whether it is empty before reading anything out of it.