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
- 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
Flow Field Performance on page
samantha73
Member Posts: 96
Hi All
I normally create flow fields for various calculated fields required for pages and reporting. My understanding is that the flow fields are triggered for only the records displayed on a page rather than the whole table. For example, say we have a flow field on posted sales invoices and the underlying table contains 1000 records. Now when we open the posted sales invoice list page it shows 20 records. Is it right to assume the system only calculates flow fields for the 20 records? A related question/assumption is there is no expressly defined table locking functions so assume it's being taking of when running a p[age or a report. When used to create reports in SQL server with stored procs I'd use NOLOCK to ensure write operations aren't affected (whether that actually happen or not is another question)
I normally create flow fields for various calculated fields required for pages and reporting. My understanding is that the flow fields are triggered for only the records displayed on a page rather than the whole table. For example, say we have a flow field on posted sales invoices and the underlying table contains 1000 records. Now when we open the posted sales invoice list page it shows 20 records. Is it right to assume the system only calculates flow fields for the 20 records? A related question/assumption is there is no expressly defined table locking functions so assume it's being taking of when running a p[age or a report. When used to create reports in SQL server with stored procs I'd use NOLOCK to ensure write operations aren't affected (whether that actually happen or not is another question)
0