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
Sift levels to maintain in nav 2009 R2 and 2013
Bgestel
Member Posts: 136
Question?
When you do a text export of the 2009 R2 OR 2013 Cronus database, and you take a look at for example Table 32.
you will see that certain keys for ex. "Item no open variant code positive location code posting date" Have the property siftlevelstomaintain defined.
I know that in previous versions you had the posibility to define these in the development client. I was under the impression that since we now have VSIFT index views this property became obsolete.
So:
Why are they still there?
Do they still affect the sift levels?
Can i just ignore them in a merge?
Is there any way left to manipulate them using the client?
I'm confused :-k
When you do a text export of the 2009 R2 OR 2013 Cronus database, and you take a look at for example Table 32.
you will see that certain keys for ex. "Item no open variant code positive location code posting date" Have the property siftlevelstomaintain defined.
I know that in previous versions you had the posibility to define these in the development client. I was under the impression that since we now have VSIFT index views this property became obsolete.
So:
Why are they still there?
Do they still affect the sift levels?
Can i just ignore them in a merge?
Is there any way left to manipulate them using the client?
I'm confused :-k
**********************
** SI ** Bert Van Gestel **
**********************
** SI ** Bert Van Gestel **
**********************
0
Comments
Look at table 380 - the key "Vendor No.,Initial Document Type,Document Type,Entry Type,Posting Date" doesn't have any SIFTLevels defined, but still has a non-default value.
Do you know if these SIFTLevels serve any purpose, still?
Jan Hoek
Product Developer
Mprise Products B.V.