Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Connect 2026! Turn data into bold moves, April 13 -15: Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

The executeUpdate method must not return a result set.

I am trying to import a csv file into MS SQL. I have a setup the mapping and I am able to insert records successfully. However if the record exists I get the error. The executeUpdate method must not return a result set. In the tMap I am importing the primary key as well and the schema of output table has the primary key defined. In the DBOutput I have specified the Action on data to Insert or update. I am assuming this handles the decision to insert or update based on the primary key being present in the table or not. Is this correct?
Labels (3)
1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

Hello,

Is there any update for your issue? Does AFTER UPDATE trigger cause this issue?

Best regards

Sabrina

View solution in original post

6 Replies
Anonymous
Not applicable
Author

Hello,

Could you please also post your tMap component setting screenshot on forum?

Best regards

Sabrina

Anonymous
Not applicable
Author

Hi Sabrina, I have attached the tMap screenshot.
tmap.PNG
Anonymous
Not applicable
Author

Hello,

Is there a trigger setting on the table? If so, are you able to change it?

Best regards

Sabrina

 

Anonymous
Not applicable
Author

Hi Sabrina, There are 4 triggers on the table and one of the AFTER UPDATE trigger seems to cause the exception. If I disable that trigger then I do not get this error. There is another AFTER UPDATE trigger that does not cause an issue. I will need to investigate the culprit trigger do find out where the issue arises. Thanks.
Anonymous
Not applicable
Author

Hello,

Is there any update for your issue? Does AFTER UPDATE trigger cause this issue?

Best regards

Sabrina

Anonymous
Not applicable
Author

Hi Sabrina, Yes one of the AFTER UPDATE trigger was causing the error to occur. After I disabled the trigger the error went away.