Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 304 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Ambiguous error when inserting records - 2013 R2 - bug?
piedmont
Member Posts: 6
Hi,
Using a GET statement in the OnInsert table trigger is giving me an unexpected result in 2013 R2. Code example - taken from some custom code on the Vendor table:
In an old (classic) database i'm upgrading, this gives the expected and quite friendly error:
Leaving aside whether it's a good way to assert existence of a user setup record... (I quite like this pattern personally..) In 2013 R2 the same code gives:
Bizarrely the debugger still displays the old error.
This seems to me like a platform bug. Anyone disagree with this (e.g. it's by design)?
Thanks
Piedmont
Using a GET statement in the OnInsert table trigger is giving me an unexpected result in 2013 R2. Code example - taken from some custom code on the Vendor table:
OnInsert() UserSetup.GET(USERID);
In an old (classic) database i'm upgrading, this gives the expected and quite friendly error:
User Setup User ID 'PIEDMONT' does not exist
Leaving aside whether it's a good way to assert existence of a user setup record... (I quite like this pattern personally..) In 2013 R2 the same code gives:
The record that you tried to open is not available. The page will close or show the next record.
Bizarrely the debugger still displays the old error.
This seems to me like a platform bug. Anyone disagree with this (e.g. it's by design)?
Thanks
Piedmont
0