From: Tarek Demiati on
I've got a customer for which I've developped a bunch of dataports for
importing and exporting data.

I've tried to automatized the import/export by setting up the Job Queue
module, however I ran into a silly problem, the job queue is returning me
the following error :

"You cannot use C/AL variables of type DATAPORT when running the Microsoft
Dynamics NAV Application Server."

From the job queue I did setup Codeunit X to be scheduled, and it's within
Codeunit X that Dataport Y is executed ...

My main constraints are that the dataports import quite complicated file
structure and it took me 3 months to develop and test, so I can't really
tell my customer that we must through away all this work ...

How come the Job Queue(Version 5) is not able to perform what the Job
Scheduler(Version 4) was able to do which is scheduling a dataport ?

Does anyone know if there's a work around to this problem ?





From: DaveT on
Hi Tarek,

You can use reports that call one or more dataport as dataport can't be call
from the job queue. The job schedule has changed in version 5 to run through
the application server (NAS). You could try to manually update the job
scheduler object to run on version 5 if your more comfortable with it.

Hope this helps


"Tarek Demiati" wrote:

> I've got a customer for which I've developped a bunch of dataports for
> importing and exporting data.
>
> I've tried to automatized the import/export by setting up the Job Queue
> module, however I ran into a silly problem, the job queue is returning me
> the following error :
>
> "You cannot use C/AL variables of type DATAPORT when running the Microsoft
> Dynamics NAV Application Server."
>
> From the job queue I did setup Codeunit X to be scheduled, and it's within
> Codeunit X that Dataport Y is executed ...
>
> My main constraints are that the dataports import quite complicated file
> structure and it took me 3 months to develop and test, so I can't really
> tell my customer that we must through away all this work ...
>
> How come the Job Queue(Version 5) is not able to perform what the Job
> Scheduler(Version 4) was able to do which is scheduling a dataport ?
>
> Does anyone know if there's a work around to this problem ?
>
>
>
>
>