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
- 309 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
Web Services - Notes and queries
eYe
Member Posts: 168
Thus far, problems I am having with WS (NAV2009W1 - Not SP 1) in a C# project:
1. Cannot have a disabled field on a table that is being accessed (even if it is a table that is being used way down the line in code - I promise the disabled field is not being referenced!) - You get an error message: The metadata for Table xyz is in a malformed state ... Field User Name must be enabled. And no, compiling object and refreshing web reference does not help. You have to remove the disabled fields entirely...?
2. You cannot have a blob field on a page that you are publishing as a web service - you won't be able to add it as a web reference in visual studio. (get a very long, unclear xml error)
3. Error messages that are too long that are thrown in NAV, **sometimes** causes unexplained/unexpected results - still need to tie this one down.
4. If all fields that compose the primary key are not on the page object, you will not be able to use the .READ(...) function in VS. only .READMULTIPLE(...)
5. In NAV all
Does anyone know if atleast #1 from above is fixed with SP1?
Hope this helps anyone else struggling as I have...
Regards,
Ewald
1. Cannot have a disabled field on a table that is being accessed (even if it is a table that is being used way down the line in code - I promise the disabled field is not being referenced!) - You get an error message: The metadata for Table xyz is in a malformed state ... Field User Name must be enabled. And no, compiling object and refreshing web reference does not help. You have to remove the disabled fields entirely...?
2. You cannot have a blob field on a page that you are publishing as a web service - you won't be able to add it as a web reference in visual studio. (get a very long, unclear xml error)
3. Error messages that are too long that are thrown in NAV, **sometimes** causes unexplained/unexpected results - still need to tie this one down.
4. If all fields that compose the primary key are not on the page object, you will not be able to use the .READ(...) function in VS. only .READMULTIPLE(...)
5. In NAV all
MESSAGE(...);have to be replaced with
IF NOT ISSERVICETIER THEN MESSAGE(...);I presume the same goes for CONFIRM(...).
Does anyone know if atleast #1 from above is fixed with SP1?
Hope this helps anyone else struggling as I have...
Regards,
Ewald
Kind Regards,
Ewald Venter
Ewald Venter
0
Comments
I added one to a table that is the source table of a page that I published as a web service that was working (did not add that field to the page object), and I was unable to Update the Web Reference.
Ewald Venter
Curiously...
I have NAV 2009 SP1. I have disabled Balance flowfield in Customer table. If I try to create Balance flowfield in Customer Page I would not be able to do it. The error will become.
Consequently I will not be able to work with Balance field from the web service based on Customer Page.