-
Hi Jim and welcome to the forum!
I can't think of an easy way to do this using an XML form as your secondary data source. You could, however, move the user list to SharePoint and use the following tutorial to update that list from the form.
http://infopathdev.com/howto/tutorials/default.aspx?i=7bc880f391b84ea9b3b45c6fbecc07c6
-
Crazy, I didn't know they converted the XSL functions to different languages. Could you tell me this: When you check the box that says ''Show XPath'' - what do you see? I would think xdMath:Eval(, but if they converted it to German, that'd be crazy!
-
Sometimes InfoPath needs to see some sample data so that it can derive a schema for the DB - maybe this is the problem?
-
Hi TTS,
The only way I know of doing this in the designer is by creating an instance of the repeating table control for every possible combination of columns. This isn't too bad if you have a very small number of columns (<= 3), but otherwise it grows exponentially. You might be able to use custom XSL in a preserver block to accomplish this ...
-
Hi Holly and welcome to the forum!
Do you mean you are adding rows or columns? I would think if you add rows in the repeating table the total should work automatically, but I could be wrong.
Could you provide us with a quick layout of your schema?
-
Hey Deb,
You can edit the template.xml file directly if you extract the form files. Try this:
1. Select Extract Form Files from the File menu
2. Select a folder and extract them
3. Browse to that folder
4. Double-click template.xml to open it in InfoPath
5. Make your edits to the question fields using normal InfoPath UI.
6. Save the ...
-
Hey Shaun, and welcome to the forums!
I haven't actually implemented this, but it should be easy to do without code. Can you give the below example a try. If this doesn't work I'll be surprised be we can work around it. Thanks!
<?xml version=''1.0'' encoding=''UTF-8''?>
<Batch OnError=''Continue''>
<Method ID=''1'' ...
-
Hey Javier,
I posted a reply on the other thread, you might want to check it out and move the whole discussion over there.
-
Hey Bill,
Here's an idea:
1. Create a boolean node in a secondary dom called ''fieldXedited'' - defaults to false
2. Set conditional formatting on fieldX in the Main DOM to be blue/red depending on value of ''fieldXedited'' on 2DS
3. Add an OnAfterChange event on fieldX that sets ''fieldXedited'' to true.
-
Also, remove the ''Cannot be blank'' attribute from the node. You will be using only this custtom data validation.