-
FormatDateTime(DATE, 2) will format the date with slashes in the order month, date, year (e.g. 7/21/2009), but an XML date must be of the form YYYY-MM-DD, i.e., year, month, date separated by hyphens and with padding zeros where necessary. FormatDateTime does not seem to have the option to format a date this way, so it may make sense to ...
-
Repeating Section vs. Repeating Table should make no difference here. They're just two ways of displaying the data. Most likely this is a capitalization problem with one of your node names inside the For Each area. Which line is line 302?
-
Yes, certainly. You just need to use the proper XPath. If this is the correct path to your repeating nodes:/dfs:myFields/dfs:queryFields/tns:Z_RFC_PR_CREATE_EX/IT_PRITEMS/item
Then you would want to use something like:XPathNavigator lastNode = ...
-
There is no way to access or modify InfoPath controls' display properties in code.
-
There is another thread on this forum reporting a similar environment-dependant issue with the same error message:
http://www.infopathdev.com/forums/t/3856.aspx
and an oh-so-helpful (not) Experts Exchange item as well
http://www.experts-exchange.com/Software/Office_Productivity/Office_Suites/MS_Office/Q_23135195.html
You might want to ...
-
e.Source refers to the node of the section that contains the button. If the button is in a repeating section, then e.Source is the repeating node, but if it is outside the repeating section, then e.Source will be a node outside the repeating data.
As I already asked, how would you define "current row?" I'm ...
-
If the button is not located in the repeating section, how do you intend for InfoPath to know what the "current" row is? What do you consider to be the current row?
-
If you are using the InfoPath 2007 object model, then the current node of a repeating section would be e.Source, where e is the ClickedEventArgs parameter of the event handler.
-
In order to use a database alias, please surround the alias with pound signs in your query, so in this case, use #prsdb# instead of just prsdb. Your web.config looks ok as it is.
-
Placing checkboxes in their own sections and hiding the sections seems to be the typical way of hiding checkboxes. This question has come up several times before and that has always been the resolution as far as I can remember.