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
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 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
Web Services ignore Provider ID on linked subpages
ichladil
Member Posts: 68
Hello,
I wanted to create a page that shows Sales Header (Order), related Sales Lines , for each Sales Line related Reservation Entries in separate list parts on the same page. I also want to expose such a page as a web service.
It was not difficult to achieve this behaviour in RTC client using ProviderID on Reservation Entries pointing to Sales Lines list. So in RTC client the page works as expected.
However when I have published such a page as a web service and wanted to read the sales order the following issues raised:
1) The ReservationEntry and Sales Line subpage are linked also by "Reservation Entry"."Source Ref. No." = SalesLine."Line No." - however web services when reading the sales order complains that I have to use integer as Source Ref. No. This seems to be caused by the fact that Sales Line."Line No." (integer) is field4 and field4 in sales header corresponds to Bill-to Customer No (Code). Web Services seems to be ignoring ProviderID and taking the link values from the header only!
2) Also ReservationEntry."Source Sub Type" = SalesLine."Document Type" = SalesHEader."Document Type". However webservice complains that value must not be Order (in Source Sub Type) and it must be 0,1,2,3... (which are actual option values on Source Sub Type). Well I have bypassed this limitation by using constant value for Source Sub Type - but more flexible solution would be better.
Any hints on how I may achieve the desired functionality using standard NAV web services?
Thanks,
Igor
I wanted to create a page that shows Sales Header (Order), related Sales Lines , for each Sales Line related Reservation Entries in separate list parts on the same page. I also want to expose such a page as a web service.
It was not difficult to achieve this behaviour in RTC client using ProviderID on Reservation Entries pointing to Sales Lines list. So in RTC client the page works as expected.
However when I have published such a page as a web service and wanted to read the sales order the following issues raised:
1) The ReservationEntry and Sales Line subpage are linked also by "Reservation Entry"."Source Ref. No." = SalesLine."Line No." - however web services when reading the sales order complains that I have to use integer as Source Ref. No. This seems to be caused by the fact that Sales Line."Line No." (integer) is field4 and field4 in sales header corresponds to Bill-to Customer No (Code). Web Services seems to be ignoring ProviderID and taking the link values from the header only!
2) Also ReservationEntry."Source Sub Type" = SalesLine."Document Type" = SalesHEader."Document Type". However webservice complains that value must not be Order (in Source Sub Type) and it must be 0,1,2,3... (which are actual option values on Source Sub Type). Well I have bypassed this limitation by using constant value for Source Sub Type - but more flexible solution would be better.
Any hints on how I may achieve the desired functionality using standard NAV web services?
Thanks,
Igor
0
Comments
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
I am aware about the alternative solutions I may use. In the case that I cannot make it working with pages as it is, it's maybe up to somebody from Microsoft to either make it working with ProviderID, or make it ignoring the subpages linked via ProviderID (so that I cannot see these as classes in .NET), or make it fail (this is perhaps worst option) in the way that it is clear that ProviderID is not supported. I just consider the current behavior the bug as I cannot use such a published page at all.
Regards,
Igor
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.