Automation variable in NAV 2015 not running with NAS

(0) Share

Report

Posted on by Community Member

Hello guys,

I am facing a problem with Automation variable. We had a Automation variable (making use of our COM) in Nav 2009 R2 and we used to run it from Client as well as on Server (using NAS) with out facing any problem.
We use

OK := CREATE(TestAutomationVariable, TRUE, TRUE); //Client COM instance

To create the Automation variable.

We have now upgraded to Nav 2015. With the upgrade we are able to run the Automation variable from Client side but when we try to run it from Server side (using NAS) we are facing an error

Microsoft Dynamics NAV
---------------------------
Microsoft Dynamics NAV Server attempted to issue a client callback to create a Automation variable. Client callbacks are not supported on Microsoft Dynamics NAV Server.

This was running fine on Nav 2009 R2.
Can any one help ?
What is the exact meaning of 'Client Callbacks' ? (I have a general idea - window popups, user input dialog's)
Were client callbacks allowed in Nav 2009 R2 and now in Nav 2015 they have stopped the support? I have read that Nav has stopped support for Server side automation Variable from Nav 2013 . But again we are creating a Client side Automation Variable.

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (4)

Verified answer

Mohana Yadav 61,005 Super User 2025 Season 2 on at

Like (0)

Report

Generally when we run automation variable in RTC then it will show us a screen to run this time, run always etc.

May be you are receiving such a screen while running with NAS and those kind of actions are not allowed in NAS

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi,

But if this was the case , we should be getting the same error in Nav 2009 R2 as in 2009 version also there was this pop-up screen.

Was this reply helpful? Yes No
Verified answer

Mohana Yadav 61,005 Super User 2025 Season 2 on at

Like (0)

Report

you need to use DotNet variable in NAV2015.

I am not sure whether we get this screen in NAV2009xx..

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi ,

Thanks for the quick reply.

As you suggested and many posts suggest, i have tried to use the dotnet variable as well.

But i get the same error.

Microsoft Dynamics NAV

---------------------------

Microsoft Dynamics NAV Server attempted to issue a client callback to create a DotNet object. Client callbacks are not supported on Microsoft Dynamics NAV Server.

---------------------------

OK

---------------------------

Was this reply helpful? Yes No
Verified answer

keoma 32,729 on at

Like (0)

Report

client callbacks were never supported, because when running on the server/nas, there is no user to react on the error/message/warning/confirm, ...

in your case that means, a function call of the automation runs into a user interaction point.

so you have to change the code (e.g. using GUIALLOWED).

in general on newer nav versions (>= 2013) better use .net assemblies instead and also be aware, that there are no user interactions will be created.

when using dotnet variables on the server/nas set property RunOnClient to false. RunOnClient=True will run into an error in that case.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Saurabh,

Did you get a solution to resolve Callback issue using .Net variable,

Please post.

Was this reply helpful? Yes No
Verified answer

Binesh 7,885 on at

Like (0)

Report

Hello saurabhab,

I think you declared DotNet variable with RunOnClient = TRUE property.

But if you set true, it will run only RTC.

Note

The Microsoft Dynamics NAV Web client does not support running the .NET object on the client.

Do one thing, post your Dotnet Variable or requirement so may be you will get alternate solution for that.

Was this reply helpful? Yes No
ManishS 86 on at

Like (0)

Report

If you are executing this via job queue then place the dll file in the service addon folder, and if you want to run this from client then place this in you RTC addon folder and change the property of RunOnClient to yes.

Was this reply helpful? Yes No