D
danmincu
Hi,
I have an XML schema where an optional attribute has the xs:IDREF
type. The attribute represents a many to many objects relationship and
the fact that the attribute is optional reflects the fact that can be
an object entity with no relation. Somehow MS Infopath, when importing
the schema, is forcing the "cannot be blank" option for any control
that represents this attribute and currently I haven't found a
workaround. What am I doing wrong? I've seen a normal behaviour when
the attribute type is not IDREF. And generally speaking what is the
appropriate approach for modeling the many to many relashioships if not
ID and IDREF?
Thank you,
Dan M.
I have an XML schema where an optional attribute has the xs:IDREF
type. The attribute represents a many to many objects relationship and
the fact that the attribute is optional reflects the fact that can be
an object entity with no relation. Somehow MS Infopath, when importing
the schema, is forcing the "cannot be blank" option for any control
that represents this attribute and currently I haven't found a
workaround. What am I doing wrong? I've seen a normal behaviour when
the attribute type is not IDREF. And generally speaking what is the
appropriate approach for modeling the many to many relashioships if not
ID and IDREF?
Thank you,
Dan M.