Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
DOTNET object -> RunOnClient:Yes
AitorEG
Member Posts: 342
Hi everyone,
After different upgrade for different customers, I've found an issue that makes me a little mess. I'll try to explain myself, and I hope you'll give me your thoughts.
Everything has to see with the development of the "Electronic VAT Information under SII", but I think that happens with every development with DOTNET objects.
I've made an upgrade for one customer to the NAV2017, and the development works perfectly, without changing any property of the DOTNET variables.
But instead, with another upgrade from other different client, doesn't happen the same.
In this case, I'm doing an upgrade to the NAV2018 version. When I try to run a development with DOTNET objects, I'm finding the error: "Cannot serialize DOTNET object". For one integration I've developed with external WebServices, I've solved this issue changing the RunOnClient property to "Yes", and I think that this issue, for the "Electronic VAT Information under SII", could be solved in the same way.
The thing is that I don't understand why this development run without changing anything in one server, and in this new one, I'm finding this issue.
Could be because of something in the server? Or the NAV installation? Any thoughts?
Thnak you all
After different upgrade for different customers, I've found an issue that makes me a little mess. I'll try to explain myself, and I hope you'll give me your thoughts.
Everything has to see with the development of the "Electronic VAT Information under SII", but I think that happens with every development with DOTNET objects.
I've made an upgrade for one customer to the NAV2017, and the development works perfectly, without changing any property of the DOTNET variables.
But instead, with another upgrade from other different client, doesn't happen the same.
In this case, I'm doing an upgrade to the NAV2018 version. When I try to run a development with DOTNET objects, I'm finding the error: "Cannot serialize DOTNET object". For one integration I've developed with external WebServices, I've solved this issue changing the RunOnClient property to "Yes", and I think that this issue, for the "Electronic VAT Information under SII", could be solved in the same way.
The thing is that I don't understand why this development run without changing anything in one server, and in this new one, I'm finding this issue.
Could be because of something in the server? Or the NAV installation? Any thoughts?
Thnak you all
0
Comments
E.g.: DotNet XMLDocument (RunOnClient=false) assigns its result to another variable XMLRootElement (RunOnClient=true).
xStepa
Appreciated!
Blog - rockwithnav.wordpress.com/
Twitter - https://twitter.com/RockwithNav
Facebook - https://facebook.com/rockwithnav/
xStepa
Only when is required some interaction with user's computer
//Just for these multiple words I used GUIALLOWED.I was pointing to this sense only.
Blog - rockwithnav.wordpress.com/
Twitter - https://twitter.com/RockwithNav
Facebook - https://facebook.com/rockwithnav/