Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.6K 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
- 272 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Document webservice page - Assign number Series for new doc
fehstcomp
Member Posts: 4
Hi all,
I have the following scenario:
- Dynamics Nav 2009 Classic client
- Dynamics Nav Web services
- Published a Transfer Header page (Page ID 5740) as a web service.
- We have two different number series for Tranfers, one for internal transfer and other for consignments for customers.
I'm trying to create a Transfer document via the webservice (using a C# application I'm developing, which uses the webservice), but I need the transfer to have a number in the number series for the consignments, and when I call Webservice.Create() it always assigns a number in the internal transfer number series.
I've tried modifying the "No. Series" field via C/SIDE on the Page but it ignores whatever i put in there and keeps assigning the next number from the "wrong" series.
It also ignores whatever is on the object which is passed to the Create method of the webservice.
I have searched mibuso and other sites, but I've been unable to find a way to sort this out. It is the only thing which is preventing me from having a working application, which is needed to streamline consigment generation from the orders, but I need to create a transfer document on the correct number series.
Any ideas?
Thanks in advance for any help.
Regards,
Antonio
[NOTE: I have posted this also in the NAV Classic topic but I've seen now that I should have posted it here.]
I have the following scenario:
- Dynamics Nav 2009 Classic client
- Dynamics Nav Web services
- Published a Transfer Header page (Page ID 5740) as a web service.
- We have two different number series for Tranfers, one for internal transfer and other for consignments for customers.
I'm trying to create a Transfer document via the webservice (using a C# application I'm developing, which uses the webservice), but I need the transfer to have a number in the number series for the consignments, and when I call Webservice.Create() it always assigns a number in the internal transfer number series.
I've tried modifying the "No. Series" field via C/SIDE on the Page but it ignores whatever i put in there and keeps assigning the next number from the "wrong" series.
It also ignores whatever is on the object which is passed to the Create method of the webservice.
I have searched mibuso and other sites, but I've been unable to find a way to sort this out. It is the only thing which is preventing me from having a working application, which is needed to streamline consigment generation from the orders, but I need to create a transfer document on the correct number series.
Any ideas?
Thanks in advance for any help.
Regards,
Antonio
[NOTE: I have posted this also in the NAV Classic topic but I've seen now that I should have posted it here.]
0
Comments
If i'm not wrong someone already post similar question on forum. Webservice.Create() method is ignore your per-defined value. In order to get your requirement you can do below method.
1. Separate the page and define the "No. Series" for each type. But it's hard code and it will work for 2 no. series.
You need to assign the no. series at "On New Record Trigger" in the page and amend the code inside the Table as well.
2. Use the code unit and create the doc. base on your requirement and read back the doc. in your app and process the other step.
Best Regards,
Yukon