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
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 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
SetRange/FindFirst VS Get to find a record
samantha73
Member Posts: 96
Hi
To find a record using the primary key we can use setrange/findfirst or Get. What are the differences between these two patterns? Does get throw an error if the primary key not found while findfirst in setrange will not error?
Thanks
To find a record using the primary key we can use setrange/findfirst or Get. What are the differences between these two patterns? Does get throw an error if the primary key not found while findfirst in setrange will not error?
Thanks
0
Answers
When you know entire primary key, it's usually better to do Get for performance.
However! If you intend to pass the record into a report, then use SetRange on PK fields as report datasets operate on filtered records - using Get and passing it to a report will make the report run on entire table as if it wasn't filtered.