InfoPath Dev

Hi, this is a 1st post and I apologies if you have already answered this question previously but couldn#%92t find any reference. I am very new to Share point and InfoPath and now know enough to be dangerous.

After reading your tutorial

http://infopathdev.com/howto/tutorials/default.aspx?i=075c4e8e56db4fa5bd63615b712c0d91

And emulating it completely I thought id try and simulate the same but utilising share point.

I have created a list with the same Year/Make/Model data and created the relevant connections so the data can be viewed within the dropdowns, however when I apply the filters they don#%92t seem to work.

If the xpath entry is /dfs:myFields/dfs:dataFields/dfs:Vehicles_-_Flat_data_Source/@Year will the filter not(. = ../preceding-sibling::Vehicle/@year) still work?

Hi ccarter,

not sure what you mean by a list, a sharepoint list? Anyway, is there any reason you couldn't do this using xml? I did this myself with a hierarchical datasource and uploaded the xml file to sharepoint. In the case of xml the vehicle/@year refers to the year attribute of the vehicle element. Not sure that a list could have such a structure...

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

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.

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)

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.

Many thanks guys works a charm

Glad to be of help!

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

 

 

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.

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 

 

 

 

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.

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.

 

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.

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