Skip to main content
Announcements
A fresh, new look for the Data Integration & Quality forums and navigation! Read more about what's changed.
cancel
Showing results for 
Search instead for 
Did you mean: 
dapharsyde
Contributor

SugarCRM output does NOTHING - always OK even if login is blank

Hi everyone - I am new to Talend, but have worked with many other ETL tools in the past.  I have a simple job that maps an Excel file to a SugarCRM custom module.  I am using the tSugarCRMOutput object, and Talend always reports this component as being successful, but no records are being loaded in SugarCRM.  Strangely enough, I have tried removing the username, password, and also provided an intentionally incorrect module name ("poop"), yet Talend always reports the component as being OK.

My assumption is that this connection is not actually working, but I cannot figure out why - especially since Talend keeps reporting the component as completing OK.  The only way I can get this component to error out is by replacing the SugarCRM Webservice URL with something invalid.

Can anyone help me with this?

0683p000009MGGR.png

Labels (2)
2 Replies
dapharsyde
Contributor
Author

I should also mention that I was able to set up a tSugarCRMInput component with the same custom module, and this component would fail if I did not provide a valid login ID.  Once I provided valid credentials, this component was successful in extracting the data from the custom module to a CSV file.  Unfortunately, when I try to do the reverse, and insert data into this custom module using the tSugarCRMOutput connector, it never does anything except report "component OK".

0683p000009MGHE.png
dapharsyde
Contributor
Author

Figured out the problem - it was an incorrect password in the tSugarCRMOutput component.  Unfortunately, this component always shows "OK" regardless of any errors it encounters.  I assume this is a bug in the tSugarCRMOutput component - this is extremely frustrating to troubleshoot, and probably needs to be fixed.
Of course, I doubt anyone will actually read this, so this will probably continue to be a problem...