AL Language: Import Proprietary Files

StLi
Member Posts: 83
Hi,
We're about to upgrade one of our customers to BC, and - to streamline updates in the future - We're rebuilding all his customizations as extensions. - Not for appsource, but so we don't have to worry about customized standard tables aso.
Most of it works fairly well, but there is a problem on the horizon I'm not sure how to solve yet: Importing/exporting proprietary files. To my knowledge, AL Language can't receive Data from files directly and the System Object "FILE" doesn't exist anymore. I know here are solutions to receive and send Files per WebService.
But is there anything available to just get a file processed, that's sitting on the Users Harddisk? Or, vice versa exporting data into a proprietary file?
I know i COULD build a C/AL based codeunit just to handle the files, but this will defeat the whole "move to extensions" approach.
Ty for your input
We're about to upgrade one of our customers to BC, and - to streamline updates in the future - We're rebuilding all his customizations as extensions. - Not for appsource, but so we don't have to worry about customized standard tables aso.
Most of it works fairly well, but there is a problem on the horizon I'm not sure how to solve yet: Importing/exporting proprietary files. To my knowledge, AL Language can't receive Data from files directly and the System Object "FILE" doesn't exist anymore. I know here are solutions to receive and send Files per WebService.
But is there anything available to just get a file processed, that's sitting on the Users Harddisk? Or, vice versa exporting data into a proprietary file?
I know i COULD build a C/AL based codeunit just to handle the files, but this will defeat the whole "move to extensions" approach.
Ty for your input
0
Best Answer
-
To develop for SaaS solutions, you have to use AppSource (and provide full documentation, a dedicated web site etc.) . MS does not permit other ways of deployment unless it's an app for on-prem. For the latter you can set the target parameter in the app.json to 'internal' which will enable the normal file handling again, as well as the use of DotNet etc.Kai Kowalewski6
Answers
-
To develop for SaaS solutions, you have to use AppSource (and provide full documentation, a dedicated web site etc.) . MS does not permit other ways of deployment unless it's an app for on-prem. For the latter you can set the target parameter in the app.json to 'internal' which will enable the normal file handling again, as well as the use of DotNet etc.Kai Kowalewski6
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions