Hi
unfortunately there is no supported way to do this as isSingleValued is
itself
system only and so cannot be modified post on attributeSchema.
I do not
know the details about what choices were made when implementing default
schema in AD certainly looking at some of the later revisions of X.5xx some
of the choices in AD schema now look over constrained. I suspect anything
that looked like it might used as naming attribute was required to be single
valued
as AD (DS or AM) does not support multi-valued RDNs but that's just
speculation
on my part.
Lee Flight
"drm" <> wrote in message
news:d7e8927b-1276-4f51-832a-...
> Is there any way to change ADAM so that the Locality-Name, Postal-
> Code, State-Or-Province-Name and Street-Address attributes are multi-
> valued on a new build? Our CTO wants us to create a customer ODS
> using ADAM and some of our customers have more than one address. He
> wants us to use x.500 attributes as much as possible. Based on what I
> have seen regarding this standard, these are the attributes that I
> should use, if I want to store the parts of the address separately.
|
Similar Threads
Linear Mode
