DSXchange

DS job has lookup stage with one i/p link one o/p link and 3 reference links.

One of the three reference links has fl_dt and row_id fields with fl_dt as key.

to change the logic the key column fl_dt in reference link was replaced with src_id.

I got desired results but job is finished with two warnings.
Here are the warnings

Lookup_1043: When checking operator: On input data set 1: The view adapter has a binding for the non-existent destination field "FL_DT".
Lookup_1043: When checking operator: On input data set 2: The view adapter has a binding for the non-existent destination field "FL_DT".

The job is running on 4 node configuration.

I was not able to fix this warnings, then included fl_dt in the reference link as key field..but still getting above two warnings.

Not sure how to fix...
guys pl help...

Have you managed to Search DSXchange for this particular message?

Found 8 other posts that mention "The view adapter has a binding for the non-existent destination field", see if any of them help.

Hi Ray,

Yes, I tried search several times for this message, even I tried with several combination like
When checking operator: On input data set 1: The view adapter has a binding for the non-existent destination field
then tried When checking operator: On input data set 1
also tried The view adapter has a binding for the non-existent destination field
and then with On input data set 1: The view adapter has a binding for the non-existent destination field
but no luck..

What I am doing now is..I exported as .dsx and opened in ultraedit
seared dsx file for fl_dt and trying to figure out if this field name exists at inappropriate place..
I removed them and importing this job..I will execute and see what happens.. I will keep u posted..

chulett wrote:Found 8 other posts that mention "The view adapter has a binding for the non-existent destination field", see if any of them help. ...

My bad..yes searching with the above phrase returns results..

thanks...

Another Solution :-

1.Tick the Column (Which was causing the warning) as a Key .
2. Compile (Better Force Compile)
3. UnTick
4. Compile (Better Force Compile)

Warning will be vanished.

yesterday i had the same issue.
I have deleted , reimported the columns and force compiled.
No more warnings after that

also have a check if the job/stages are using RCP

most of the times,this warning will come even if RCP is disabled.
The main thing is OSH needs to be refresshed with new code(when copying stages).
so,Force compile helps.

yes if RCP is diabled but the column is still fused in the score of the job, but at times people correct the metadata but still the warning exists due to RCP.

what was posted is just one chance of its occurence