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
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 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
MyNotification - Filter Problem with "@" RTC
Troubles_In_Paradise
Member Posts: 588
Hi guys. Today our customer contacted us because he send to his colleagues some notification but no one can see them.
We tried with our user and we can see his notification but he cannot see our notification for him.
we asked him to send us a screenshot of the filters applied to the RecordLink (the records for notifications are correctly populated) table by the MyNotification standard part on the Role Center:
we opened the table RecordLink table and we tried the following.
1. set the filter (@chzemxk1|@Company\chzemxk1) on the "To User ID" field no rows come out... :shock:
2. set the filter (chzemxk1|Company\chzemxk1) on the "To User ID" field and notification rows come out...
3. set the filter (@MyID|@MyCompany\MyID) on the same field rows come out...
4. set the filter (MyID|MyCompany\MyID) on the same field and the rows come out...
the only difference between my id and customer's id is that my is completly uppercase his is completly lowercase, but "@ is used to not be Case-Sensitive" isn't it?
the other test I did is to filter the user setup table for User ID. if I filter with "@ no rows come out... without @" the row come out.
do you have any suggestion? Am I missing something?
Thx in advance.
We tried with our user and we can see his notification but he cannot see our notification for him.
we asked him to send us a screenshot of the filters applied to the RecordLink (the records for notifications are correctly populated) table by the MyNotification standard part on the Role Center:
we opened the table RecordLink table and we tried the following.
1. set the filter (@chzemxk1|@Company\chzemxk1) on the "To User ID" field no rows come out... :shock:
2. set the filter (chzemxk1|Company\chzemxk1) on the "To User ID" field and notification rows come out...
3. set the filter (@MyID|@MyCompany\MyID) on the same field rows come out...
4. set the filter (MyID|MyCompany\MyID) on the same field and the rows come out...
the only difference between my id and customer's id is that my is completly uppercase his is completly lowercase, but "@ is used to not be Case-Sensitive" isn't it?
the other test I did is to filter the user setup table for User ID. if I filter with "@ no rows come out... without @" the row come out.
do you have any suggestion? Am I missing something?
Thx in advance.
~Rik~
It works as expected... More or Less...
It works as expected... More or Less...
0
Answers
http://blogs.msdn.com/b/nav/archive/2011/11/25/few-tips-about-filters-usage-in-latest-dynamics-nav-rtc-builds.aspx
-Mohana
http://mohana-dynamicsnav.blogspot.in/
https://www.facebook.com/MohanaDynamicsNav
Interesting but doens't help us. Thanks anyway.
Now we're checking the options under Database Alter menu to see if could be caused by something there.
I'll let you know.
It works as expected... More or Less...
doesn't work with:
Collation: Windows Collation
Collation Description: Czech [compatibility]
Validate Collation: False
Case Sensitive: False
Accent Sensitive: True
works with:
Collation: SQL Collation
Collation Description: Czech dictionary sort order, code page 1250, case-insensitive, accent-sensitive (84)
Validate Collation: False
Case Sensitive: False
Accent Sensitive: False
It works as expected... More or Less...