General

Re: Repeating Cascading List from Sharepoint

Sam — Tue, 13 Nov 2007 08:03:47 GMT

Hi,

I have an XML list and i am working on the repeating cascading list on my Infopath form.

I have a price value and i would like to keep it on the list as inactive but not shown under the drop list on my form..

Any ideas.

Hetal

Re: Repeating Cascading List from Sharepoint

Greg Collins — Mon, 23 Jul 2007 16:21:54 GMT

Again, these work just the same as any other cascading list.

1. Create a secondary data source by connecting to your SharePoint list.
2. Evaluate the structure returned (i.e. the SP List DOM created by InfoPath) for the fields you are interested.
3. Create the cascading list from those fields (it sounds like you've already done a cascading list before--so just follow similar steps).

Re: Repeating Cascading List from Sharepoint

Sam — Mon, 23 Jul 2007 11:59:22 GMT

I meant a custom list on the sharepoint site.. - lists, document libraries..thast what i mean..

Re: Repeating Cascading List from Sharepoint

Greg Collins — Wed, 18 Jul 2007 20:32:15 GMT

Hi. I don't understand this part: "using a custom or datasheet list". What do you mean by those choices? A cascading list is done using the List Box control or the Drop-Down List Box control.

Re: Repeating Cascading List from Sharepoint

Sam — Tue, 17 Jul 2007 09:29:20 GMT

I agree with you. I just dont want to give users permissions to fiddle with the XML sheet - I have a price option in the cascading list.

Thought if users could changes prices in the list and i can take it from there.

Can you please tell me how are cascading list done using a custom or datasheet list.

Re: Repeating Cascading List from Sharepoint

Greg Collins — Mon, 16 Jul 2007 22:53:14 GMT

It's just a secondary data source either way, whether an XML file or a SharePoint list. So it doesn't make much of a difference.

The SP list will likely have a different structure/hierarchy than the custom XML file you are using now, so you have to account for that... but the concept is identical no matter what the source.

Re: Repeating Cascading List from Sharepoint

Sam — Mon, 16 Jul 2007 08:20:38 GMT

Hi,

As of now i have items being pulled from an XML document to the cascading list.

I dont know how items can be pulled from a list to a cascading list.

Since changes are going to be made very often, i want users to make changes on a custom list which automatically makes changes on the XML doc and the results reflect on my cascading list.

Hope that makes sense now..

Thanks

Re: Repeating Cascading List from Sharepoint

Greg Collins — Wed, 11 Jul 2007 21:18:27 GMT

Hi, I don't fully understand your scenario.

1. You have items used in a cascading list which are pulled from a SharePoint list. Okay -- following so far.

2. Its will be changing often, and you want the changes to take place in the SharePoint list. -- still following so far.

3. Want to move items from the SharePoint list to an XML document -- not following any more.

Re: Repeating Cascading List from Sharepoint

Sam — Mon, 09 Jul 2007 11:02:55 GMT

Hi,

I understand the entire cascading list with hierarchical data source and it works perfect.

This is what i want to do:

1. All my items are stored on a Sharepoint list.

2. From the SP list i want items to be moved to an XML document.

Since the values will be changing very often, I dont want users to be playing with the XML document. They just need to go to the SP list and make changes.

Will this be possible. I have seen a similar question above but no one seems to have answered..

Thanks

Re: Repeating Cascading List from Sharepoint

Greg Collins — Tue, 23 May 2006 21:59:13 GMT

Glad to be of help!

Re: Repeating Cascading List from Sharepoint

ccarter — Tue, 23 May 2006 01:59:54 GMT

Many thanks guys works a charm

Re: Repeating Cascading List from Sharepoint

SamDahl — Mon, 22 May 2006 23:52:30 GMT

Thanks for the hint Greg, got my test one working now.
the filter still needs the preceding-sibling test:

not(. = ../preceding-sibling::dfs:Vehicles_-_Flat_data_Source/@Year)

similarly the next two dropdowns will be

not(. = ../preceding-sibling::dfs:Vehicles_-_Flat_data_Source[@Year = current()/my:Year]/@Make)

and

not(. = ../preceding-sibling::dfs:Vehicles_-_Flat_data_Source[@Year = current()/my:Year and @Make = current()/my:Make]/@Model)

assuming the datasource:
Vehicles_-_Flat_data_Source
----Year
----Make
----Model

note: @Datasource items are from the 2DS where my:Datasource items are from the main datasource. Be sure to only change the relevant ones.

Goodluck.

Re: Repeating Cascading List from Sharepoint

Greg Collins — Mon, 22 May 2006 16:49:03 GMT

Hi ccarter,

You listed that you were attempting to use:

/dfs:myFields/dfs:dataFields/dfs:Vehicles_-_Flat_data_Source/@Year

the filter:

not(. = ../preceding-sibling::Vehicle/@year)

won't work because you do not have a "Vehicle" node any more. Your node is now named "dfs:Vehicles_-_Flat_data_Source". Also "@year" is now capitalized to "@Year". You must always account for such name changes or XPath differences.

With this in mind you might try something like:

not(. = ../dfs:Vehicles_-_Flat_data_Source/@Year)

Re: Repeating Cascading List from Sharepoint

SamDahl — Mon, 22 May 2006 06:42:56 GMT

You can have the xml file loaded into sharepoint and thus use it elsewhere etc. admittedly a list is a little easier to maintain than an xml file. I'm presently trying to replicate your situation using the tutorial and a list in place of the xml datasource. I'll post the result tomorrow. I haven't yet applied the filter but being a list and not xml I have doubts that it will work.

Re: Repeating Cascading List from Sharepoint

ccarter — Mon, 22 May 2006 05:09:28 GMT

Many thanks Sam. what i have done is create a list with 3 columns , as you would in an excel spreadsheet. If i maintain the list within Sharepoint i can utilise it elsewhere and have a centraly managed dataset - a little easier to maintain than an xml file