InfoPath Dev

I think this is a basic question to understand InfoPath 2007 and it's datasource mechanism.

- I have a field "projectLead" (type:string, directly under "myfields" folder). I can use an expression control and the xpath: my:projectLead and the field contents display properly as expected.  However, if I set up a text field control and set the default value to be the same projectLead it shows the xpath as: ../my:projectLead and doesn't display anything.  If I try to manually change the xpath to say my:projectLead I get an error saying that the path doesn't point to a valid location.

What am I missing here?

Your expression box is most likely sitting in a section bound to a node higher up the tree than your text box. So, definitely, the expression box would use the XPath my:projectLead and your text box would use ../my:projectLead. The ../ is taking you up the tree - so let's say your text box is bound to a field under the myFields folder called my:leadName - you'd need to go up to myFields (../) then to the project lead field (my:projectLead), giving you ../my:projectLead.

Now, as to why the value isn't showing in your text box - well, it should. Your text box isn't also bound to the my:projectLead field, is it? Can you attach your template to the Options tab so I can take a quick peek at it?

I've attached a quick sample form that duplicates the issue.  The read only view has the expression box displaying data and the text box not. 

Thanks!

Do you have all your service packs installed? I ask because this form behaves as anticipated for me.

Ug, I hate when stuff like this happens, cause now it's working fine for me.  However when I opened up the form I originally tested with it was still not working.  Oh well, at least I'm not going crazy, glad it's working in one instance, I have no idea what could have changed from one to the other, I didn't do anything significant that I'm aware of.

The original one just to show I wasn't being insane.

Think I figured it out.  I was adding this to existing forms and using this as a default value for a text field, which would pretty much only apply to new BLANK forms that would require a DEFAULT value :-/.