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
Changing Collation Issues
martinhocosta88
Member Posts: 27
Hello,
I had one database with following collation: Latin1_General_100_CS_AS. (Case Sensitive, Accent Sensitive)
I needed it to be Case and Accent Insensitive so I've created a new database with the collation Latin1_General_100_CI_AI and then exported/imported the data via powershell before synchronizing the data.
So now on RTC everything looks normal except on Search Field where I am not able to make accent insensitive searches. (but it works well on filters and on other fields)
Is there anything that I am missing?
I had one database with following collation: Latin1_General_100_CS_AS. (Case Sensitive, Accent Sensitive)
I needed it to be Case and Accent Insensitive so I've created a new database with the collation Latin1_General_100_CI_AI and then exported/imported the data via powershell before synchronizing the data.
So now on RTC everything looks normal except on Search Field where I am not able to make accent insensitive searches. (but it works well on filters and on other fields)
Is there anything that I am missing?
0