Hello Friends,
This blog is only relevant to Technical Developer of Dynamics NAV.
While we doing an upgrade project we have prepare a single merge text file contain all the old version customization and we need to import this text file new standard version base database.
While import the file we have face different type of error - because something wrong during merge or may be there is some text issue in old code.
I have summarize all the possible error during import files and solution for that.
Because some time it is very difficult to identify the issue in merged files.
This blog is only relevant to Technical Developer of Dynamics NAV.
While we doing an upgrade project we have prepare a single merge text file contain all the old version customization and we need to import this text file new standard version base database.
While import the file we have face different type of error - because something wrong during merge or may be there is some text issue in old code.
I have summarize all the possible error during import files and solution for that.
Because some time it is very difficult to identify the issue in merged files.
1) Error for “//” written in
description field
Error:
---------------------------
Microsoft
Dynamics NAV Development Environment
---------------------------
There is a
syntax error in the import on line 220749 in position 2 : KEYS.
A '{'
(ElemBegin) is expected here.
---------------------------
OK
---------------------------
Error
Reason:
There is
double slash written in field description
Solution:
Remove that
double slash from description field.
=======================================================================
2) Syntax Error (TAB
Character exists in text constant )
Error:
---------------------------
Microsoft
Dynamics NAV Development Environment
---------------------------
There is a
syntax error.
---------------------------
OK
Error
Detail:
Tab
Character in Text Constant (some time we copy paste the text from word file than it was happen)
Error
Solution:
Remove TAB
Character manually
=======================================================================
3) “OnBeforePassField”
trigger not supported in NAV 2013 and it is also not converted by conversion
tool
---------------------------
Microsoft
Dynamics NAV Development Environment
---------------------------
'Export::OnBeforePassField=12
}' is not an option.
The
existing options are:
Indentation,
Expanded, NodeName, NodeType, SourceType, ID, ParentID, NamespacePrefix,
Namespaces,
Comment, Occurrence, MinOccurs, MaxOccurs, VariableName, Format, TextType,
Width,
DataType, Import::OnAfterAssignVariable, Export::OnBeforePassVariable
---------------------------
OK
Error
Detail: OnBeforePassField” trigger not supported in NAV 2013 and it is also not
converted by conversion tool
Solution : This property not supported in new version. Skip import that xmlport and do it latter.
=======================================================================
4) Field Name is change in new version so it is giving error for : “Prod. Order No.” to “Order No.”
---------------------------
Microsoft
Dynamics NAV Development Environment
---------------------------
You
cannot enter ' { ;Prod. Order No.,Item
No.
}'
in FieldNo.
---------------------------
OK
Error
Reason:
Change
the name of field
Solution:
Fix the name of key fields
=======================================================================
5) } “Breaket” is used
instead of semi colon (;)
---------------------------
Microsoft
Dynamics NAV Development Environment
---------------------------
There is a
syntax error in the import on line 32203 in position 50
:
Description=C0011-1001330 }.
A '{'
(ElemBegin) is expected here.
---------------------------
OK
Error
Reason:
There is
should be line end with semicolon but it is ended by }
Error
Solution:
Write the
semicon in place of closing breaket
=======================================================================
6) There is keyword “VAR” is
missing before define the variable in function
---------------------------
Microsoft
Dynamics NAV Development Environment
---------------------------
'BEGIN'
should come here.
---------------------------
OK
Error
Reason:
There is
keyword “VAR” is missing before define the variable in function
Error
Solution:
Enter the
keyword “VAR” before the first variable define
=======================================================================
7) Begin and END line exists
with start procedure (it is invalid past line so check and remove it)
---------------------------
Microsoft
Dynamics NAV Development Environment
---------------------------
'.'
should come here.
---------------------------
OK
Error
Reason:
There
is invalid line files (Procedure syntax is missing before function code start)
Error
Solution:
Remove
that lines and make it correct
=======================================================================
8) Duplicate Name Found in
table
---------------------------
Microsoft
Dynamics NAV Development Environment
---------------------------
The field
name can appear only once in a table:
Field Name:
Shipping Agent Code
Table:
Service Header
---------------------------
OK
Solution:
You have added customize field with same as new standard field. So update the
name of your custom field.
========================================================================
9) You have Replace the “VAR”
keyword with “Begin” so system is doesn’t find the END for that new Begin
---------------------------
Microsoft
Dynamics NAV Development Environment
---------------------------
There is a
syntax error in the import on line 120574 in position 50 :
CaptionML=ENU=Location
Code }.
The AL code
is not indented as much as the first line.
---------------------------
OK
Error
Reason:
See the
following snapshot. Where you can find that you have replace the “VAR” Keyword
by “Begin”
In text
file it is look like
Solution:
Update that
Begin keyword with VAR keyword
=======================================================================
10) Error in Import Page File
---------------------------
Microsoft
Dynamics NAV Development Environment
---------------------------
'{
64 ;2 ;Action
;
CaptionML=ENU=Line Discounts;' is not an option.
The
existing options are:
ID, Name,
CaptionML, Caption, ToolTip, ToolTipML, Description, Image, Visible, Enabled,
RunPageMode,
Promoted, PromotedCategory, PromotedIsBig, ShortCutKey, Ellipsis, RunObject,
RunPageView,
RunPageLink, RunPageOnRec, InFooterBar, ActionLevel, OnAction
---------------------------
OK
Error
Reason: There is closing breaket is missing in new action added on page
Solution:
Merge the missing part and it will solve the error
=======================================================================
11) Error for double semicolon
in page
---------------------------
Microsoft
Dynamics NAV Development Environment
---------------------------
You cannot
enter '; } PROPERTIES { CaptionML=ENU=Service Item Card;' in FieldNo.
---------------------------
OK
Error Reason:
There is
double semicolon in data
Solution:
Remove one
to solve error
=======================================================================
12) Import Error “t_id” import
file
---------------------------
Microsoft
Dynamics NAV Development Environment
---------------------------
't_id'
should come here.
---------------------------
OK
Error
Reason:
Solution:
Added
Breaket to solve error
=======================================================================
13)
VAR
Keyword is missing before define variable
---------------------------
Microsoft
Dynamics NAV Development Environment
---------------------------
Use the
symbol { to start the comment. For example: {Ordinary comment}.
---------------------------
I will update blog when i face any new error in import.
I hope it will help you some time to get the solution of your issue.
Thank you reading.
Please write the comment if have any query/concern.
Kepp Sharing... Keep Growing...
Happy Independents Day,,,,,
Congrats, well done!
ReplyDeleteCould you tell me what are your experiences with Dynamics? Is it much different comparing to other versions of this software? I use of them at my company, provided by dynamics ax partner, AX Dynamics.
Good luck with your work.