Tuesday, July 22, 2008
OAM Search Results Virtual Attribute
What if you want to include a virtual attribute in your search results that is derived form another attribute? Just create the attribute in an outbound mapper flow and add it to the search results and it should show up as expected - right? Well, maybe it will and maybe it won't; if the attribute(s) the derived value is based on is/are in the search results too then it will show up as anticipated. However, if they are not there then it won't show up as expected.
The solution is to use the OVD
The solution is to use the OVD
addReturnAttribute delivered mapper function on the reciprocal inbound request with the required source attributes. This will allow the outbound mapper to have the required data to complete the derived attribute and enable the OAM search result configuration to exist without the source attributes.Labels: Mapper, OAM Search Results, OVD
Permalink posted by Dave Bennett @ 7:52 a.m. 
Comments:
<< Home
Hi Dave,
I am using OblixIDXML_common_search_Service to search for users, but I am only able to read DN from the results. Result set contains only one value.
I was unable to set return values using request parameters.
requestParams myparams = new requestParams();
myparams.noOfFields = "5";
but unable to set myparams.attrName value.
Am I missing something? Any example will be really helpful. Thank You.
Thanks,
Ramesh
Post a Comment
I am using OblixIDXML_common_search_Service to search for users, but I am only able to read DN from the results. Result set contains only one value.
I was unable to set return values using request parameters.
requestParams myparams = new requestParams();
myparams.noOfFields = "5";
but unable to set myparams.attrName value.
Am I missing something? Any example will be really helpful. Thank You.
Thanks,
Ramesh
# posted by 
: 6:55 p.m.
: 6:55 p.m. << Home
