DRA really ought to be able to search for e-mail addresses. Frequently I have an e-mail address for someone but that is the only unique piece of information. Sure, I can break the e-mail address apart and search for the first and last name from the e-mail address but then I frequently get a list of accounts that I have to examine to see if they are the one matching the e-mail address.

In other tools, if you are adding a lot of users to a group, a list of email addresses is much more useful than a name because it's guaranteed to be unique and its frequently easier to obtain from other sources than an account name.

I realize that e-mail addresses are not cached by DRA and therefore it can't search on them. Why not add it to the cache and make it available for searches?

by: Andrew D. | over a year ago | Miscellaneous

Comments

• Thank you for this Idea. We accept this as a valid request and will target the DRA 9.2 release to add email addresses as a search attribute.

  by: Dennis P. | over a year ago

• We also have a huge need for searching by employee ID (like in the Win32 console) in the REST Web Console. A lot of our service desk uses EMPID as the verification item for users, to give them the ability to ask the question and then search by their answer before verifying more attribute info would be beneficial for the team. It is also the only means of search option in a lot of requests from HR. They will give a request to have X information updated on EMPID 12345 which was a pull from the HR application and a pass to the service desk. Keeps them from either having to ask for a new pull with the names included or writing a powershell script to pull the user info from the employee ID so they can do what they need to in the web console.

  by: Chris H. | over a year ago

• FYI: prior to 9.1.1 we did the following to accomplish the goal. I tried the same process in 9.1.1 in my dev environment and it didn't work as expected.
  
  Files Modified
  
  
  C:\inetpub\wwwroot\DRAClient\locale\en-us\Localized.JSON
  "searchCriteriaFields": {
  "friendlyName": "Name",
  "description": "Description",
  "friendlyParentPath": "Location",
  "displayName": "Display Name",
  "clientName": "Client Name",
  "nameValue": "Name",
  "samAccountName": "Pre-Windows 2000 Name",
  "lastName": "Last Name",
  "firstName": "First Name"
  }
  
  C:\inetpub\wwwroot\DRAClient\components\lib\ui-templates\attribute-search-criteria.json
  
  {
  "fields": [
  {
  "attributeName": "samAccountName",
  "displayName": "Pre-Windows 2000 Name"
  },
  {
  "attributeName": "firstName",
  "displayName": "First Name"
  },
  {
  "attributeName": "lastName",
  "displayName": "Last Name"
  },
  {
  "attributeName": "clientName",
  "displayName": "Client Name"
  }, {
  "attributeName": "nameValue",
  "displayName": "Name"
  }, {
  "attributeName": "displayName",
  "displayName": "Display Name"
  }, {
  "attributeName": "description",
  "displayName": "Description"
  }
  ],
  
  C:\inetpub\wwwroot\DRAClient\components\lib\ui-templates\search-criteria.json
  
  
  {
  "fields": [
  {
  "attributeName": "samAccountName",
  "displayName": "Pre-Windows 2000 Name"
  },
  {
  "attributeName": "firstName",
  "displayName": "First Name"
  },
  {
  "attributeName": "lastName",
  "displayName": "Last Name"
  },
  {
  "attributeName": "friendlyName",
  "displayName": "Name"
  },
  {
  "attributeName": "description",
  "displayName": "Description"
  },
  {
  "attributeName": "friendlyParentPath",
  "displayName": "Location"
  },
  {
  "attributeName": "displayName",
  "displayName": "Display Name"
  }
  ],

  by: david s. | over a year ago

• This has been implemented in DRA 9.2. David Shoemaker => Support will follow up with you about the JSON question outside of the Ideas Portal.

  by: Dennis P. | over a year ago