Codeunit Execution

Answers

• Options

  Kishorm Member Posts: 921

  2016-10-10

  Depends on whether you are talking about older versions of NAV (2 tier) or later versions of NAV (3 tier). In older versions, the local client would be executing the codeunit whereas in newer versions it's the middle tier (NST = NAV service tier) that would be executing the codeunit.
  
  There is also the related question of where DotNet variables run (on 3 tier) - for this there is a RunOnClient property. Similarly, there is a ClientSide property when using the CREATE function to create instances of automation servers.

  1
• Options

  coheedramos Member Posts: 6

  2016-10-10

  Kishorm wrote: »

  Depends on whether you are talking about older versions of NAV (2 tier) or later versions of NAV (3 tier). In older versions, the local client would be executing the codeunit whereas in newer versions it's the middle tier (NST = NAV service tier) that would be executing the codeunit.
  
  There is also the related question of where DotNet variables run (on 3 tier) - for this there is a RunOnClient property. Similarly, there is a ClientSide property when using the CREATE function to create instances of automation servers.

  
  thanks kishorm. what about the DotNet datatypes that is calling a custom written DLL. I'm encountering an issue in creating an instance. I want the DLL to be copied in the server only not on the client machines. If I make it RunOnClient = Yes, it is creating an instance but it requires the DLL to be installed or copied on the other clients. however, if it is "No" it cannot create an instance.

  0
• Options

  coheedramos Member Posts: 6

  2016-10-10

  btw I am using NAV 2013 R2

  0
• Options

  Kishorm Member Posts: 921

  2016-10-10 Answer ✓

  If you want to run the DotNet DLL on the server only then you need to set RunOnClient to "No". If it can't create the instance then that means that the machine that is running the NST does not have the DLLs installed on it.

  5