Newbie Questions

Re: Repeating Cascade List Problem

SamDahl — Wed, 12 Jul 2006 23:04:12 GMT

It's funny in the end how it all comes down to syntax.

I'd still like to know how you got the infinite loop in a datasource...

Glad you got it working!

Re: Repeating Cascade List Problem

Taffman — Wed, 12 Jul 2006 09:01:07 GMT

I've finally managed to get this to work.
I abondoned the flat data file I created that caused the repeading datasource!! and went back to generating the XML from Microsoft Access.

In following the tutorial in http://infopathdev.com/howto/tutorials/default.aspx?i=51dce616335a4ff6a78f2d289baf4651 (yet again) I still couldnt get uniqueness to work.

I finally get it to work by replacing the following data filter:

not(. = ../preceding::my:group2/my:field2)

with:

not(. = ../preceding::group2/field2)

All seems to be working fine now.
Many thanks to everyone how has taken the time to help out here.

Re: Repeating Cascade List Problem

SamDahl — Tue, 11 Jul 2006 23:18:15 GMT

Wow, In my rather limited experience with infopath I've never seen that. You seem to have managed to put some xml inside itself.
First place I'd look is at the XML itself.
Any chance you could post it? I'm intrigued.

Matt, or someone, might have a more immediate idea of what's going on...

Re: Repeating Cascade List Problem

Taffman — Tue, 11 Jul 2006 08:02:27 GMT

This is what I see in my datasource:

The nested datasource is expanded when I click on the + symbol. You can carry on clicking the + symbol and see another nested group of data ad infinitum ?

Re: Repeating Cascade List Problem

SamDahl — Tue, 11 Jul 2006 01:43:10 GMT

quote:
but now I see the same group repeat itself, ad infinitum in the Data Source view

...not quite sure what you're indicating here, I don't think anything in the data source view should repeat itself infinately.

All I can say is, the msc_cpe_kit_list you posted is fine (I've used it successfully). If your xpaths/filters are correct, and your structure is correct, then there must be some external factor.
I can't really help you doublecheck your xpaths/filters and structure short of you posting pictures/diagrams of what you have.

Have you tried copying what I did in my previous post?

If you can copy exactly what I did (what worked for me) and it doesn't work for you then your problem must be elsewhere.

This is the exact datasource as I've used it:
<?xml version="1.0" encoding="UTF-8" ?>
<dataroot xmlns:od="urn:schemas-microsoft-com:officedata" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="msc_cpe_kit_list.xsd" generated="2006-06-06T16:26:46">
<msc_cpe_kit_list>
<cpe_vendor>CISCO</cpe_vendor>
<cpe_family>18411</cpe_family>
<country_kit>EU1</country_kit>
<cpe_code>WS1-H-C1841-PF-EA1</cpe_code>
<cpe_description>CISCO1841 + 64kbps - 1984kbps - V35 + EU AC Power cord</cpe_description>
<display>WS1-H-C1841-PF-EA - CISCO1841 + 64kbps - 1984kbps - V35 + EU AC Power cord</display>
<list_price>2495</list_price>
</msc_cpe_kit_list>
<msc_cpe_kit_list>
<cpe_vendor>CISCO</cpe_vendor>
<cpe_family>18412</cpe_family>
<country_kit>EU2</country_kit>
<cpe_code>WS2-H-C1841-PF-EA2</cpe_code>
<cpe_description>CISCO1841 + 64kbps - 1984kbps + ISDN BRI - V35 + EU AC Power cord</cpe_description>
<display>WS2-H-C1841-PF-EA - CISCO1841 + 64kbps - 1984kbps + ISDN BRI - V35 + EU AC Power cord</display>
<list_price>2995</list_price>
</msc_cpe_kit_list>
<msc_cpe_kit_list>
<cpe_vendor>CISCO</cpe_vendor>
<cpe_family>18412</cpe_family>
<country_kit>EU2</country_kit>
<cpe_code>WS2-H-C1841-PF-EA2</cpe_code>
<cpe_description>CISCO1841 + 64kbps - 1984kbps + ISDN BRI - V35 + EU AC Power cord</cpe_description>
<display>WS2-H-C1841-PF-EA - CISCO1841 + 64kbps - 1984kbps + ISDN BRI - V35 + EU AC Power cord</display>
<list_price>2995</list_price>
</msc_cpe_kit_list>
<msc_cpe_kit_list>
<cpe_vendor>CISCO</cpe_vendor>
<cpe_family>18412</cpe_family>
<country_kit>EU4</country_kit>
<cpe_code>WS2-H-C1841-PF-EA2</cpe_code>
<cpe_description>CISCO1841 + 64kbps - 1984kbps + ISDN BRI - V35 + EU AC Power cord</cpe_description>
<display>WS2-H-C1841-PF-EA - CISCO1841 + 64kbps - 1984kbps + ISDN BRI - V35 + EU AC Power cord</display>
<list_price>2995</list_price>
</msc_cpe_kit_list>
<msc_cpe_kit_list>
<cpe_vendor>CISCO</cpe_vendor>
<cpe_family>18413</cpe_family>
<country_kit>EU3</country_kit>
<cpe_code>WS3-H-C1841-PF-EA3</cpe_code>
<cpe_description>CISCO+ E1 + EU AC Power cord</cpe_description>
<display>WS3-H-C1841-PF-EA - CISCO+ E1 + EU AC Power cord</display>
<list_price>3395</list_price>
</msc_cpe_kit_list>
</dataroot>

Re: Repeating Cascade List Problem

Clay Fox — Mon, 10 Jul 2006 20:13:09 GMT

What i have found is that the syntax for the xpath statement is very critical and if it is not right you do not get an error or anything you just get duplicate values and it does not work. Here is what I have done to try and make sure my syntax is right.

When you open the initial Drop-Down Properties box. In the Entries field, if you scroll through the whole thing is the entire xpath expression that is created.

/dfs:myFields/dfs:dataFields/dfs:HR_Data_Test3/@Manager[not(. = ../preceding::dfs:HR_Data_Test3/@Manager)]
This is a sample from a form I have. As you can see the filter, within the Brackets[], must have the same syntax as the field plus the parent group to be valid.

Hope this helps or gives you a lead otherwise i have spent a lot of time troubleshooting my syntax since the only way to verify is to try it until it works.

Re: Repeating Cascade List Problem

Taffman — Mon, 10 Jul 2006 16:37:30 GMT

Still battling with this one!!!
I decided to create my secondary data source manually in the same format as the tutorial, rather than generate the XML from =Excell
I have managed to do this sucessfully (I think) but now I see the same group repeat itself, ad infinitum in the Data Source view. Top level is a ordinary group, the others are repeating?

Anyone have any idea on whats happening here?

The xml has been formatted as follows:

<?xml version="1.0" encoding="UTF-8"?>
<test_list>
<test_list family="123" code="WS11-C877-P-ADSLP" description="test description" display="Long Test Description"/>"
</test_list>

Re: Repeating Cascade List Problem

SamDahl — Tue, 13 Jun 2006 23:59:22 GMT

Hmm, it worked in mine...
What I've done:

1. copied the xml you listed here and used it as a 2DS.

2. followed the hierarchical tutorial, my main datasource looks like this:
-myFields
--Group1
---RepeatingGroup1
----Field1
----Field2
----Field3

3. doubleclicked each combobox and using "Look Up Values In A Data Connection..." I've bound the first three items from the xml. i.e:
Field1 is bound to /dataroot/msc_cpe_kit_list/cpe_vendor
Field2 is bound to /dataroot/msc_cpe_kit_list/cpe_family
Field3 is bound to /dataroot/msc_cpe_kit_list/country_kit

4. added filter to Field2 based on the value of Field1, likewise for Field3 based on Field2. (I won't copy these out because you have these working, yes? (the "current()/my:Field1" bits, etc))

5. I've then added another filter to each Field. These are the uniqueness filters:
Field1 has "not(. = ../preceding-sibling::msc_cpe_kit_list/cpe_vendor)"
Field2 has "not(. = ../preceding-sibling::msc_cpe_kit_list/cpe_family)"
Field3 has "not(. = ../preceding-sibling::msc_cpe_kit_list/country_kit)"

6. the Entries Field in the Drop Down List Box Properties dialogue boxes show, respectively:

"/dataroot/msc_cpe_kit_list/cpe_vendor[not(. = ../preceding-sibling::msc_cpe_kit_list/cpe_vendor)]"

"/dataroot/msc_cpe_kit_list/cpe_family[(../cpe_vendor = current()/my:Field1) and (not(. = ../preceding-sibling::msc_cpe_kit_list/cpe_family))]"

"/dataroot/msc_cpe_kit_list/country_kit[(../cpe_vendor = current()/my:Field1 and ../cpe_family = current()/my:Field2) and (not(. = ../preceding-sibling::msc_cpe_kit_list/country_kit))]"

7. I've tested this and indeed it works for me. For each combobox on many rows in the repeating table.

So, what have I done differently to you?

I assume your secondary datasource is the same as you've posted here
Your main datasource will be different, atleast a little, is it structurally the same, though? could you post it?
simple things like checking spelling is exactly the same, not copying the quotation marks into your code, etc
anything else you can think of that might have bearing on this function? (or lack thereof)

If that turns up nothing I'm afraid I might be at a loss...

Re: Repeating Cascade List Problem

Taffman — Tue, 13 Jun 2006 08:31:29 GMT

Nope this doesnt work either, still see duplicate values?

Re: Repeating Cascade List Problem

SamDahl — Tue, 13 Jun 2006 00:08:37 GMT

*embarrassed* ...made my test values different >.<
My apologies.

This'll work:
not(. = ../preceding-sibling::msc_cpe_kit_list/cpe_vendor)

Double-click the drop-down list box.
Click the Select XPath button to the right of the Entries text box. Select the field in the tree that you are using in this combo box (eg. msc_cpe_kit_list/cpe_vendor).
Click Filter Data, and then click Add.
In the first drop down of the Specify Filter Conditions dialog box select The Expression and input the above filter.

You should only have to change the "msc_cpe_kit_list/cpe_vendor" bits to suit other fields you wish to filter.

Re: Repeating Cascade List Problem

Taffman — Fri, 09 Jun 2006 14:02:54 GMT

Many thanks for taking the time and trouble to help. I think I do need a uniqueness filter irrespective of wether I use flat or hierarchial xml files because I still see multiple values in the first column.

Re: Repeating Cascade List Problem

SamDahl — Thu, 08 Jun 2006 23:14:36 GMT

You should be able to follow the Hierarchical tutorial. A uniqueness filter is not necessary. You don't have a /value attribute in your datasource, when the tutorial asks to select msc_kit_list/cpe_family/value just choose msc_kit_list/cpe_family. Make sure to differentiate between nodes in your secondary datasource and fields in your main datasource (current()/my:Year for example refers to the first field in your repeating table) and you should be home dry.

Post back if you need any further help, goodluck!

Re: Repeating Cascade List Problem

Taffman — Thu, 08 Jun 2006 10:55:53 GMT

quote:
Originally posted by shailaja

Hello Taffman,
Did you try another How To which is based on Hierarchical datasource. One difference between the xml used in How To based on Hierarchical data source and the xml which you sent is that he set values in attributes. The link to How To ishttp://www.infopathdev.com/howto/tutorials/default.aspx?i=9f6fda3a14c14ac4924cf0a382928432

Hope this helps!

Many thanks for this, from what I'm able to determine the only difference in this HowTo is that the Xpath statement for the datasource adds /value. My problem is that my Hierarchical datasource shown above does not display a Valuenode.

The following image show what my datasource looks like:

Re: Repeating Cascade List Problem

shailaja — Thu, 08 Jun 2006 08:08:39 GMT

Hello Taffman,
Did you try another How To which is based on Hierarchical datasource. One difference between the xml used in How To based on Hierarchical data source and the xml which you sent is that he set values in attributes. The link to How To ishttp://www.infopathdev.com/howto/tutorials/default.aspx?i=9f6fda3a14c14ac4924cf0a382928432

Hope this helps!

Re: Repeating Cascade List Problem

SamDahl — Thu, 08 Jun 2006 06:34:43 GMT

Ok, the xml you've posted is a hierarchical datasource where the tutorial you've posted uses a flat xml datasource.

If you need help adapting your uniqueness filter post what you've got and I'll take a look at it.