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 ? Sure being able to run as a service is an upgrade compared to V4 ...
Does anyone know if there's a work around to this problem ?
0
Comments
My Blog - nav.education
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
Yes it does not work either
For now on I will just install the the Job Scheduler.
I think I will no longer use dataport and develop my own mapping tool, so I've got a good generic tool that will simulate what the dataport was good for (setting the delimiter, fixe/variable lengh ...)
Many of my customers are asking me about using the Job Queue, unfortunatly many of them have got zillions of middle aged dataports ...
so, if you need to import / export Datas use a report / Codeunit or XMLPort.
Regards
If so, you're probably better off just migrating the dataports into reports that WRITE into a file. I highly doubt that MSFT will add dataports to be able to run in Job Queue anytime soon.
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book