faultDetail cannot be resolved or is not a field

[Anonymous]

Hi!

I'm very new to talent and just trying to follow some tutorials. I am using a tESBConsumer to access some web service and then connect the fault row to a tLogRow. I follow the instructions in the help page of tESBConsumer for this.

If I don't use the fault row everything works fine. Once I connect the fault row to the tLogRow to get a log of the Soap Fault I get the compile message "faultDetail cannot be resolved or is not a field".

Can someone point me in the right direction?

[vapukov]

Hi, welcome!

will be much better if You attache some screenshots of Your Job and error

it make process much more easy

best regards, Vlad

[Anonymous]

Here is a screenshot of the job with the compile errors.

If I remove the tLogRow2 it works fine. Once I connect the fault route from tESBConsumer to the tLogRow2 I always get this error...

error compiling

[vapukov]

in 99% off cases it missed "" around variable or mistake in variable name

[Anonymous]

I would agree with you but there is no configuration involved in connecting a tESBConsumer to a tLogRow. You just connect it and it should show the log for the Fault (according to the documentation)...

[vapukov]

what I know - 4 eyes better than 2 🙂

attach all config screenshot and sure we found - where the problem!

[Anonymous]

Thanks! Here are the configurations for each module.

tLogRowtESBConsumertXMLMaptFixedFlowInput

[Anonymous]

To make sure this does not have to do with the web service being invoked I leave a screenshot of the Fault WSDL created for the web service.

Fault WSDL

[cterenzi]

I think this error usually indicates a schema mismatch. Can you try pressing the sync schema button in the tLogRow config, or else delete it and replace it with a fresh one?

Side note: does Talend expose the schema for reject or error flows from components?

[Anonymous]

I think so too! I tried removing the tLogRow and then adding again but the error persists.