[AX2009]: Call a stored procedure

(0) Share

Report

Posted on by Basti Aurand

270

Hello together,

I'm currently facing a problem in MS Dynamics AX 2009. Im trying to call a stored procedure via x++ code with the following code:

The execution is successful (no errors) but the content of the stored procedure is not executed and the effect / result could not be seen in the DB.

If i run the stored procedure directly from the SQL Management Studio with the identical SQL Statement /EXEC [MY_ITEM]..../ everything is executed correctly.

Any idea why the code / the class is executed without errrors but no effect in the DB?

Thanks for any hint

Sebastian

All responses (3)

Answers (1)

Sort by

Martin Dráb 241,434 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

You seem to be saying that executeQuery() runs without error and it returns an empty result, but your code checks neither of that.

Please look at what you get from executeQuery() and then call statement.getLastError() and check its return value too.
Basti Aurand 270 on at

Like (0)

Report
Copy link

Link copied!

Hi Martin,

thanks for your response. The stored procedure copies values from AX tables to an external DB, therefore I did not check it in x++ / AX 2009. I checked the result (copied values are available or not) directly in the external database tables via the SQL management studio and I did not get any records / values when executing via x++. I extended the code a bit to get some more information:

For me everything seems fine apart from the fact that nothing is done in the SQL DB.

Any other ideas what I could try?

Sebastian
Verified answer

Basti Aurand 270 on at

Like (0)

Report
Copy link

Link copied!

After a bit of trial and error I came out with a solution. My problem was a combination of two issues:

1. You need to set the correct access rights on the stored procedure after creating it in the sql management studio (you could copy the rights from the AX standard SP "dbo.CREATESERVERSESSIONS")

2. After changing the executeQuery to executeUpdate the SP is executed correctly: