Please add employeeID as a cached attribute for all object types or make functionality available for us to cache attributes that we need. Its ridiculous that the search functions are allowed to search attributes that aren't cached. Its extremely inefficient.
I am sure other companies may have other priorities as far as cache-able attributes but it would seem that you would not want searches to be slow because DRA has to hit a DC every time instead of ADLDS. I am still confused as to how this got past development.
This is our biggest end user complaint. Slowness of searches in the web and 32bit consoles. It makes the product look bad in the eyes of end users who don't really comprehend these types of things. It doesn't matter how many times support tells us to do better queries. We have 60000+ folks at the company and probably 20-30% of them use DRA for group management. Its hard to convey the intricacies of searching to that many people. It should just work.
by: Chris L. | over a year ago | Configuration
Comments
Chris,
Thank you for the suggestion regarding the caching of employeeID. We will continue to investigate this capability as well as hear from other customers regarding this feature.
This feature will be included in the upcoming DRA 10 Web Console. As always, please continue to share your ideas in this portal, as they are vital to ensure your ideas are considered in future releases of DRA.