-
It's certainly worth a try... though I wouldn't just throw it in blindly. You should try it out on a new blank test form to make sure it works and that you understand all the requirements. Then once you have it working there, add it to your production form.
-
What are you using to develop your code in? Visual Studio should have caught the fact that "getAttribute()" is not valid... the capitalization is wrong. It should be "GetAttribute()".
If that doesn't work, you can always get an attribute value this way: node.SelectSingleNode("@Name").Value
-
I don't personally have any suggestions to speed up or automate the process.
Perhaps someone else will care to jump in here with some ideas.
-
The manifest edit is the only way that I know of to automate this. It makes it so that the filtering occurs immediately and always. That means that when you insert a new row, that new row MUST contain whatever is necessary (usually some field value on the row) to make that new row not hide as soon as it is inserted. This can be done using the ...
-
XML Standards require time to be in the format of "HH:MM:SS" (with timezone info as optional). Thus, when you have the node set to the Time data type, InfoPath does conversion for you to get a valid time enty. When the node is a String data type, InfoPath will make no such conversion attempt.
This is expected behavior.
When you dropped ...
-
More from my Microsoft contact. Looks like you'll need to call in for support if you want any further help debugging this issue:
Thanks Greg – this is certainly odd behavior but not something we have ever had a call on.
Hopefully that user will create a case so we can look into this further for them. I honestly cannot imagine this is a ...
-
Text Boxes and Expression Boxes can be set up to format as almost any data type. So likely what happened was you converted the date field into a text field (which reset it to use text formatting), but your Expression Box was still set to use Time formatting. That could have been fixed by going into the Expression Box properites dialog and changing ...
-
You have available whatever is possible using the SharePoint Web Services (see the SDK documentation for what all you can do there). And if that doesn't work, you can always create a full-trust form and do whatever you want using code.
-
Rules can only populate single values. If you want to do repeating rows of data, you will need to write code to iterate through the table, adding rows as appropriate, and filling in the row field values.
-
You are interested in the OnBeforeChange or OnValidate events.