You need to swich to some other port, check the box, than swich to Associated Expression again.
I also marked it to be ignored in comparison (which shouldn't make any difference, in fact). However I wondered what is the logic behind Update Dynamic Cache Condition vs New Lookup Row.
The Integration Service builds the dynamic lookup cache when it processes the first lookup request.
It queries the cache based on the lookup condition for each row that passes into the transformation.
The Integration Service flags the row as an update row.
The Integration Service makes no change when the row exists in the cache and you configured the Lookup transformation to insert new rows only.
The remapping values for each globally cached lookup can be specified by a json object as per the following examples: value specifies the period in ISO 8601 format between checks for replacement data for the lookup.
In such a case logs from the lookup nodes should be monitored for repeated failures.
But what if the underlying table upon which lookup was done changes the data after the lookup cache is created? The lookup will still hold the previously cached data, even if the underlying target table is changing.
Is there a way so that the cache always remain up-to-date even if the underlying table changes? You are loading your target table through a mapping. But what if you want your Informatica Lookup cache to get updated as and when the data in the underlying target table changes?
For most implementations, the discriminator for choosing the URIs is by whichever one reports the most recent timestamp for its modification time.
We want to check the dynamic cache in lookup to find out if it's newer or older than the cached one.