tMap - Die on error not working ?

[Anonymous]

Hello All,

I'm using TOS version 7.0.1.

When in my tMap, I uncheck the "Die on error" option, it changes to yellow.
Then the OK button of the window isn't greyed but does nothing anymore.
The only option I have is to press Cancel.

After that, the setup contains a little 1 in a red circle and of course, no rejected output is available.

I have then to go check the die on error option (which is unchecked, even if I pressed Cancel)...

Can you please help me ? Is this a bug or am I missing anything ??

Thanks in advance,

Fred

[manodwhb]

@FRibadeau,can you share your job and tMap settings?

[TRF]

Hi,

With previous verisons (I use 6.4.1), when you uncheck the tMap option "Die on error", you got the "1" in a red circle (as you explain) plus an new output called ErrorReject placed on top of existing output flow already in place.

If you don't have the same behaviour with 7.0.1, it sounds like a bug. 

[Anonymous]

Hi,

Thanks for your answer.

You're right, it must be a bug.

I can't click on OK and by clicking Cancel, it keeps the Die on error modification but does not create the ErrorReject Output.

Thanks anyway,

[Anonymous]

Hello,

Does this issue only repro on V 7.0.1? It looks like a bug.

Best regards

Sabrina

[Anonymous · Accepted solution]

I have the same problem :

Software versionI open the tmap propertiesI open the tmap properties.

I uncheck the "Die on error" dialog box. If I try to click or enter on "ok" nothing happens, the message box doesn't close and I can only close it by clicking on the red close symbol or on "cancel".

A "1" appear on the properties box and there is no error reject table.

If I open the properties again I can see that the "Die on error" box is unchecked and I still can't click on ok.

[Anonymous]

So it seems to be an error occurring only with the 7.0.1 version of TOS because when i use the 7.0.1 version the table is not there and if I try to use the 6.5.1 version, the table is showing up properly.

[Anonymous]

Hello All,

We created a jira issue to log this bug.

https://jira.talendforge.org/browse/TUP-20851

I will keep you posted.

Best regards

Sabrina