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
- 264 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
ERROR in hybrid environment 'Symbol reference generation failed in application object'
micieboris
Member Posts: 7
Hi Everybody,
for the people who have issues regarding compiling objects in a hybrid environment (eg: NAV2018 C/AL & AL), and are getting the following error: 'Symbol reference generation failed in application object xxxxx, line xx, message Begin expected'.
This error happens due to the 'generatesymbolreference=yes' parameter in the finsql.exe.
Not that you need to remove this parameter, but it makes the Development interact with AL (symbols generation). And apparently in the XML port, there is a issue(bug) where C/AL doesn't complain about, but AL does. When I export my XML-port that is generating this error to text, I can see there is a trigger added to an 'element' line, that actually belongs to a 'field' line. This trigger is not visible in the XMLport Designer.
Maybe the Source Type of the Node was changed during development, at one time, but nevertheless, it is giving an error when you try to compile this object, with the generatesymbolreference turned on.
Fix is to delete the line, and add it again.
for the people who have issues regarding compiling objects in a hybrid environment (eg: NAV2018 C/AL & AL), and are getting the following error: 'Symbol reference generation failed in application object xxxxx, line xx, message Begin expected'.
This error happens due to the 'generatesymbolreference=yes' parameter in the finsql.exe.
Not that you need to remove this parameter, but it makes the Development interact with AL (symbols generation). And apparently in the XML port, there is a issue(bug) where C/AL doesn't complain about, but AL does. When I export my XML-port that is generating this error to text, I can see there is a trigger added to an 'element' line, that actually belongs to a 'field' line. This trigger is not visible in the XMLport Designer.
Maybe the Source Type of the Node was changed during development, at one time, but nevertheless, it is giving an error when you try to compile this object, with the generatesymbolreference turned on.
Fix is to delete the line, and add it again.
0