Newbie Questions

Re: preventing duplicate values in a repeatable section

aruna akella — Fri, 21 May 2010 06:24:05 GMT

Preceding means it contains all nodes that are before the context node in document order. Look at my previous post link where I did something similar to what you asked - but you need to modify the rule to make it work for the repeating section.

Hope that helps!

Re: preventing duplicate values in a repeatable section

tgnielsen — Fri, 21 May 2010 06:22:35 GMT

That is a little bit of genius Qazi. Thanks :)

Re: preventing duplicate values in a repeatable section

Qazi Anis — Fri, 21 May 2010 05:32:09 GMT

check attachment

Re: preventing duplicate values in a repeatable section

tgnielsen — Fri, 21 May 2010 02:17:27 GMT

Thanks for taking a look. I know about the preceding tag, but it only applies to one preceding sibling as I understand it. Is there a way to the comparison for multiple fields ?

Re: preventing duplicate values in a repeatable section

Patrick Halstead — Thu, 20 May 2010 17:15:24 GMT

Rules can be copied in ShP 2010. One of the cool new features! :)

Re: preventing duplicate values in a repeatable section

aruna akella — Thu, 20 May 2010 14:39:23 GMT

Can you go through this post? - and see if it helps you.. Definitely you cannot copy the rule, but see if you can modify and make it work for your repeating section.

preventing duplicate values in a repeatable section

tgnielsen — Thu, 20 May 2010 09:42:27 GMT

Hi guys,

I'm have some difficulties with my infopath form. I want to produce an XML file with the output based on a well defined XSD.

Basically the issue is that I have a structure like this:

<xs:element name="Profiles">

<xs:complexType>

<xs:sequence>

<xs:element ref="Profile" minOccurs="1" maxOccurs="unbounded"/>

</xs:sequence>

</xs:complexType>

</xs:element>

<xs:element name="Profile">

<xs:complexType>

<xs:sequence>

<xs:element ref="Nodes" minOccurs="0" maxOccurs="1"/>

</xs:sequence>

</xs:complexType>

</xs:element>

<xs:element name="Nodes">

<xs:complexType>

<xs:sequence>

<xs:element ref="Node" minOccurs="1" maxOccurs="unbounded"/>

</xs:sequence>

</xs:complexType>

</xs:element>

<xs:element name="Node">

<xs:complexType>

<xs:attribute name="basePort" use="required" type="xs:string"/>

<xs:attribute name="hostName" use="required" type="xs:string"/>

<xs:attribute name="name" use="prohibited" type="xs:string"/>

</xs:complexType>

</xs:element>

A Profile should be able to have multiple Node elements, but the hostName attribute for each should be unique. I've added the following Data Validation rule to the hostName field in my form, but its seems to evaluate that I have multiple entries for hostName, not whether they are the same value:

count(/Profiles/Profile/Nodes/Node[@hostName = /descendant-or-self::node()/@hostName]) > 1

Has anyone got any ideas of how I can prevent the hostNames for a Profile from being duplicated ?

regards,

Trevor