-
This are a custom area inside the XSL files that are user-editable via the designer, but not to the level you are talking about.
The first suggestion would be to shorten the hint text so that it doesn't need to wrap.
Outside that, if you want to modify these, you will need to go into the XSL files, locate them, and make your modifications there. ...
-
Specifically what links are you referring to?
-
Maybe this will help:
http://www.infopathdev.com/forums/topic.asp?TOPIC_ID=1834
-
That's the code I wrote earlier where it uses the ''[]'' filter. You make this selection into your other form's DOM (as per the example you already downloaded).
-
No, no. Preceding-sibling doesn't work the way you are trying to use it. It needs to start from your current selection (i.e. eventObj.Source). You're trying to make it go all the way back to the root node, which has NO preceding siblings. And you need to also use it on a Repeating Node (i.e. the table row itself), not an Attribute.
So it would be ...
-
Ah, okay. So what you need to do is to get the current row of your current table, so that you know which row to update in your second form.
You can do this using the preceding-sibling:: axis. This would be something like:
var rowNumber = eventObj.Source.selectNodes(''preceding-sibling::my:RowNodeName'').length + 1
Then use rowNumber to set the ...
-
Have you seen this article? Use the SharePoint '[Me]' Filter with a Promoted Property
http://www.infopathdev.com/blogs/greg/archive/2005/09/08/Use-the-SharePoint-_27005B00_Me_5D002700_-Filter-with-a-Promoted-Property.aspx
-
Is the issue that the node is ''blank'' or the node is ''not present'' because that is a big difference.
Blank nodes should not pose any problem to you, and setting their value should work fine. However, null nodes (i.e. not present in the DOM) this is a ''by design'' issue. You can't set the value of a node that doesn't exist. First you must ...
-
-
So you are getting a new page per row? This should not be the case. I know the article was written for InfoPath 2003. Are you using 2007? If so, there could be an issue in the article between the two versions. Let me know. If you are on 2003, try following through the article a second time to see if that fixes the issue.