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
- 270 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
NoSeriesManagement.INITSERIES
CGaralde
Member Posts: 19
Hi,
I just have a question regarding an error that I am encountering regarding the INITSERIES function in the NoSeriesManagement codeunit.
I am getting the error:
"Type conversion is not possible because 1 of the operators contains an invalid type. Code := Text"
My code is:
My scenario is:
From my limited knowledge in NAV, I know that the first, second and last parameters all refer to the NoSeries.Code. So I was just trying to hardcode the default, old and new series code to 'OB-SO' instead of creating a field which basically points to the same thing. Now when I try to compile, I get the "type conversion" error on the last parameter.
Any help is appreciated.
I just have a question regarding an error that I am encountering regarding the INITSERIES function in the NoSeriesManagement codeunit.
I am getting the error:
"Type conversion is not possible because 1 of the operators contains an invalid type. Code := Text"
My code is:
NoSeriesMgt.InitSeries('OB-SO','OB-SO',0D,"SO Link",'OB-SO');
My scenario is:
From my limited knowledge in NAV, I know that the first, second and last parameters all refer to the NoSeries.Code. So I was just trying to hardcode the default, old and new series code to 'OB-SO' instead of creating a field which basically points to the same thing. Now when I try to compile, I get the "type conversion" error on the last parameter.
Any help is appreciated.
0
Answers
Looks like "SO link" causing the issue. This should be a code type field so what is it?
On a sales header table the same call is:
NoSeriesMgt.InitSeries(GetNoSeriesCode,xRec."No. Series","Posting Date","No.","No. Series");
If it is not this field, please send your number series table and confirm which version of Nav you are using.
Neil
Thanks for taking the time. First of all, I am using Nav 2013 R2.
Anyway, "SO Link" is defined as CODE[15] on Rec. I know that the error is on the last parameter because when I change it to, let's say Rec."No. Series" then no error appears.
I do use the same parameters as the Sales Order, in my earlier projects but my gripe with my current scenario is, the first, second and last parameters are all CODE[10] then why is it only showing an error on the last parameter.
Thanks.
Not sure I can help then. It does look odd so may be worth checking latest list of bugs for Nav 2013R2.
The last but one parameter should be a code 20 -at least it should in the GB version - as this is the document number which is always as far as I am aware code 20. But then if you pass code 15 it will cope.
Only other think is where is "SO Link" coming from? Which table?
Neil
"SO Link" is in my customized Order Book table. It basically meant to hold the SO (Sales Order Confirmation) Document number and therefore link the Order Book with the Confirmation, hence "SO Link".
Again, my main problem is why the error of Type Conversion Code:=Text when:
-Isn't Code directly convertible to Text?
-'OB-SO' as a parameter value is not accepted, when 'OB-SO' as a value, in Rec table, in No. Series field is accepted?
-DefaultNoSeriesCode, OldNoSeriesCode accepts 'OB-SO' while NewNoSeriesCode does not?
I am stumped. ](*,)
that error message might be misleading. Actually, that last parameter is a VAR parameter. You cannot supply a text constant.
Thanks vaprog! I am a a bit of a newbie at this and you are right, it is a VAR parameter. Actually, I did not know about VAR parameters until you pointed it out. So a VAR parameter only accepts references and not values. You learn something new everyday.
Thanks again everyone for the help.