Run X++ static method in CIL using runClassMethodIL

(0) Share

Report

Posted on by maram fraij

I try to use the below code to run static method in X++ in CIL but I face the error shown below where Request for the permission of type 'XppILExecutePermission' is failed although the permission is asserted . how can I solve this issue ?

3618.Untitled.gif

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (1)

Sort by

Martin Dráb 240,055 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Try running your code on server. Adding "server" keyword to a job doesn't make the job to run on server.

Was this reply helpful? Yes No
maram fraij on at

Like
a
(0)

Report
Copy link

Link copied!

The code is executed on the server itself .

Was this reply helpful? Yes No
Martin Dráb 240,055 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

No, it isn't, if you just run the job.

Was this reply helpful? Yes No
maram fraij on at

Like
a
(0)

Report
Copy link

Link copied!

I execute the job on the server where AX service is running .

Was this reply helpful? Yes No
Martin Dráb 240,055 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Ah, sorry, I thought you would already know (after a few years working with AX) that X++ can be executed at two different "tiers". One is the client tier, which is physically represented by the client process, ax32.exe. The other is the server tier, or AOS (ax32serv.exe).

If you look at the call stack, you'll see (C) at the line with your job. It means that it was executed on client (by the client application), not on server (by the AOS).

Was this reply helpful? Yes No
maram fraij on at

Like
a
(0)

Report
Copy link

Link copied!

So what Should I do to enforce the job to be executed on the server ?

Was this reply helpful? Yes No
Verified answer

Martin Dráb 240,055 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

The best approach is not using a job at all; you'll have to move your code to a class before deployment anyway (because no real business logic belong to jobs), so you can start with a class straight away. A class can be configured to run on a specific tier, or you can use SysOperation framework to collect input on client and execute business logic on server.

A workaround (strictly for development purposes) is creating a menu item with RunOn = Server and execute the job through it, but creating a class is less work.

Was this reply helpful? Yes No