topic Re: [resolved] Component uses default context value instead of just loaded one in Talend Studio

[resolved] Component uses default context value instead of just loaded one

Anonymous — Sat, 16 Nov 2024 10:26:18 GMT

Hello,
I'm loading context from a csv file in a prejob and after it is loaded I print it with tjava component and it shows me a correct value.
However when I try using it in a tSalesforceGetUpdated as a start and end dates, the component seems to use the default dummy values instead of just loaded ones.
Does anyone has any idea how to fix this?
Any help is very much appreciated!

Gabriele

Re: [resolved] Component uses default context value instead of just loaded one

Anonymous — Tue, 23 Aug 2016 04:48:51 GMT

Hi,
Could you please give us your job setting screenshots? In this way, we can see if there is something wrong with your setting.
Best regards
Sabrina

Re: [resolved] Component uses default context value instead of just loaded one

Anonymous — Tue, 23 Aug 2016 10:01:36 GMT

Hello, of course: So the dates are correct in the context that I load, but too early in the defaults. It seems like context values are set, but the component still uses the defaults.

Re: [resolved] Component uses default context value instead of just loaded one

Anonymous — Tue, 23 Aug 2016 10:08:53 GMT

Are you sure that the default dates are being used or is that an assumption? Could you set the default dates to the ones you think are correct (the ones you are setting using the tContextLoad) and let us know what happens?

Re: [resolved] Component uses default context value instead of just loaded one

Anonymous — Tue, 23 Aug 2016 10:14:09 GMT

Yes, if I put the same dates I load in context as default values then it runs:

Re: [resolved] Component uses default context value instead of just loaded one

Anonymous — Tue, 23 Aug 2016 10:39:24 GMT

OK. here used to be an issue with setting context variables in code (in tJava) components that would happen like this, but you are using the tContextLoad. This is strange. The only thing I can think of adjusting is to link your subjobs using the OnSubJobOK connectors rather than the OnComponentOK connectors. If that makes a difference, this could be a bug.

Also, could you show us how the Salesforce component is configured if the above doesn't solve your issue.

Re: [resolved] Component uses default context value instead of just loaded one

Anonymous — Tue, 23 Aug 2016 10:49:02 GMT

I changed to onSubjobOk links - nothing changed.

Also, if I do not set any default values for context variables, then it throws an error :

in the java code:

it seems ir can't find any value. Altough tJava component can successfuly print loaded values, but the Salesforce component can't see it.

Re: [resolved] Component uses default context value instead of just loaded one

Anonymous — Tue, 23 Aug 2016 10:50:27 GMT

Yes, the component configuration:

Re: [resolved] Component uses default context value instead of just loaded one

Anonymous — Tue, 23 Aug 2016 11:27:50 GMT

Thank you for your help.
I still don't know why the loaded context can't be reached from the tSalesforceGetUpdated component, but
I was able to get the functionality I needed by setting global Map variable in the tJava with the loaded context value:
globalMap.put("LastCheck", context.timeLast);
and writing expression directly in the tSalesforceGetUpdated component field:
Start Date: (String)globalMap.get("LastCheck")
End Date: TalendDate.getDate("CCYY-MM-DD hh:mm:ss" )

Re: [resolved] Component uses default context value instead of just loaded one

Anonymous — Tue, 23 Aug 2016 11:42:58 GMT

This appears to be a bug with the component. https://jira.talendforge.org/browse/TDI-36865

Just saw your post. Given the description of the problem in their Jira, I am surprised that works. However, if it does that's great!