Newbie Questions

Re: Cascading list problem

Anonymous — Wed, 29 Oct 2008 10:06:47 GMT

Ahh, it's all so clear now - think my head must have been clouded from staring at notepad too long!

When I looked at both again I realised that in my code I had failed to refer to the actual "Authorised" group, I was able to solve the problem by simply changing it to:

Thanks again for all your help Hilary - definitely the quickest (and most useable) advice I've had from this site :)

Re: Cascading list problem

Hilary Stoupa — Tue, 28 Oct 2008 18:38:19 GMT

Well, actually, there is a pretty big difference between yours and the sample. In yours, you have an element called Funding. If you want the element of funding to have the value of 'No', it would look like this:

Notice that there is no longer any space between the words 'Cheque' and 'Value' -- we don't put spaces in attribute or element names. ChequeValue and AuthBy are now attributes of the Funding element. If we look at the Vehicles sample:

Here we see that there are 3 attributes to the Vehicle, year, make and model. There is no value set in the Vehicle element itself. To do the same with your example, perhaps we'd add an attribute of 'Approved' (since that is my best guess of the 'No' value for funding... ) like so:

Re: Cascading list problem

Anonymous — Tue, 28 Oct 2008 18:12:16 GMT

Hoping you can help me out a little bit more - I've used the example file and altered it as necessary to utilise in my form. It's all been done in notepad and the formatting is identical to the example you sent me but when I'm trying to add the .xml file as a data source I keep getting the below error message :(

The form contains XML that cannot be parsed:
A name contained an invalid character.

Line 3, Position 12
<Funding="No" Cheque Value="Under 500" AuthBy="Adrian Grant"/>

It seems to think the = sign is an invalid character but I can't see how as it's used in the example code. I thought it may be something to do with formatting or font but I've tried copying the = sign directly from the example code you gave me and still get the error. I've attached a copy of the ,xml file, if you wouldn't mind looking over it to see if you can figure out what I'm doing wrong it would be hugely appreciated!

Re: Cascading list problem

Anonymous — Tue, 28 Oct 2008 14:45:26 GMT

Yay, it works! Thanks so much Hilary - I knew it would be something simple and had tried pasting in notepad but not saved it with the .xml extension :)

Re: Cascading list problem

Hilary Stoupa — Tue, 28 Oct 2008 14:29:40 GMT

Hi there -- try pasting the xml into a simple text editor, like notepad, and saving it with a .xml extension. In fact, I'll attach a copy to this post for you, so you can just right click the link and select 'Save As' to get a copy.

Hope that helps....

Cascading list problem

Anonymous — Tue, 28 Oct 2008 13:20:34 GMT

Hello, I'm working with a new form that will need to utilise a cascading list. In order to get my head around this, I've been trying to use the "How To" guide on creating a cascading list from a flat data source but I'm encountering problems just going through the guide. I've copied the code and pasted into a word doc which I've then saved as a .xml file and then added the file as a data connection onto my new blank form. The problem is occurring when it comes to populating the DDL with the data connection. When I come to step 4 (Click the Select XPath button to the right of the Entries text box, select Vehicles/Vehicle/year, and then click OK twice to close the open dialog boxes.), I don't get the options of Vehicles/Vehicle/Year but rather get a load of data from the word document - it still looks like a data source but follows the below layout:

-WordDocument

-macrosPresent

-embededObjPresent

-ocxPresent

etc..

Any ideas as to what I'm doing wrong? The DDL is not repeating and is really quite a basic cascade as there are only 2 levels but I can't seem to figure this out.

http://www.infopathdev.com/blogs/greg/archive/2005/07/06/Create-a-Cascading-List-from-a-Flat-Data-Source.aspx