Howdy, Stranger!
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
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
XML Port permission issue
armela
Member Posts: 20
I am using an XML port where I will import a bank file to create Deposit lines.
Along with that, I am going to the Customer Ledger entries and setting the Amt. to Apply to match the amount that the bank file is sending me.
In a dataport I would go to properties -->Permission and assign Read and modify permissions to table 21. When I do the same thing on an XML port, my XML crashes and it logs me out of NAV.
Has anyone done smth like this where they had to modify records in Ledger entries via an XML and if so how ??
An update to this: It has been fixed in the latest Build. So it is not a programming issue, but excecutable issue ,
Along with that, I am going to the Customer Ledger entries and setting the Amt. to Apply to match the amount that the bank file is sending me.
In a dataport I would go to properties -->Permission and assign Read and modify permissions to table 21. When I do the same thing on an XML port, my XML crashes and it logs me out of NAV.
Has anyone done smth like this where they had to modify records in Ledger entries via an XML and if so how ??
An update to this: It has been fixed in the latest Build. So it is not a programming issue, but excecutable issue ,
0