Frank, I am a bit confused here.
Whether the search is case sensitive or case insensitive is either a DB setting (in the case of Sybase or SQL Server) or a config option you give us to set some options in the DB (Oracle and there are all kinds of qualifications on the case insensitivity there). Then, depending on the setting, we make sure that filter and active link qualifications are performed in a case sensitive/insensitive manner matching what the DB configuration is. The key is that we don't do a case sensitive or insensitive search -- the DB is the one that controls that based on the configuration. Then, couple that with your note that this is a Vendor form. We do not do the search at all with a Vendor form. We pass the search to your plugin code and that code does the search. We don't control whether that search is case sensitive or case insensitive. Now, given that this is LDAP, there is one question that comes up.... Did you write the plugin or are you using the LDAP/AD plugin that is provided with the AR System? This is significant as it determines where the code that is actually doing the search is from -- is it from BMC or from your side. This plugin code is what is in charge of how the search in the datasource works. If it is the BMC written plugin, this would be a support request to see how the search is being performed. And if you have your environment configured to be a case in-sensitive database, there is a good chance that the BMC plugin is picking that up for consistent interaction with other forms. Now, if it is picking up this setting but you don't want it to because you want case insensitive interaction for all other forms but just this ONE form case sensitive.... Then, you may need to have your own plugin (unless we put in an option to override being consistent) to control the Vendor form search. I hope this is helpful, Doug Mueller -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Frank Caruso Sent: Monday, November 19, 2012 7:01 AM To: [email protected] Subject: ARDBC Unique Column ARS 76.04 SP2 Created a vendor form to our LDAP directory using the "cn" attribute as the unique column (mapped Request ID to cn). I was told by the admins that "cn" would be unique for all users. However, what I am seeing is that the "cn" value is kept unique by making the value either all upper case, lower case or a mix of upper and lower cases letters. For example, "JOE SMITH" and "Joe Smith" are considered unique in LDAP. I can perform searches using the vendor form and get multiple results but when I toggle between each entry the values on the screen do not change. Remedy uses the "cn" value to retrieve the details and does not do a case-sensitive search but does a case-insensitive search and returns data for the first entry found. Base on the Joe Smith example I get two results but can only see details for the first record found. Is there a setting in Remedy that I can set to make the search case-sensitive? Thank you. Frank _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
