-
If you aren't afraid to work with your form's source files, you can modify the manifest to do this - see this blog post.
qRules also has a command for this (among tons of other commands that can prevent having to add custom code to your form).
-
Yup - under tools / form options you can disable this in the Open and Save category (if you are using IP 2010, Form Options is on the File tab)
-
In the same location you added your repeating group 13 times, you can drill down into each repeating group and set different defaults for the fields. So, if you had 13 instances of a group called Group1, and it has a field called Field1 inside it, each instance of Field1 could have a different value.
-
You can do this with a condition that a count of the preceding-sibling nodes = 0. See attached sample - right click the link in the heading of this post, save the file locally. Right click the saved file and select design to open in design mode. From there, preview.
-
The form template has a schema which determines the structure of the XML created by the template.
When you look at the main data source for your template - that's the schema.
More ...
-
It seems like you may have been able to use a repeating schema - but you would have ended up adding instances to the form's defaults to include all the "days" - that is, you'd have a repeating Day group, perhaps, with a Week field (so you could have 1 or 2) and a DayId (so you'd have Mon-Sun or their day numbers)... and ...
-
Did you change your mapping? The mapping file no longer points to a repeating group, thus the ID parameter would have to be the full path to the ID node instead of a relative path. Your current mapping file has "my:myFields" for the repeating group - your previous mapping file had my:myFields/my:Items/my:Item
Here's the mapping ...
-
I think the message is pretty clear - the rich text field control in your browser form is not supported in Firefox. This link claims that there is full functionality in browser forms in Firefox 1.5 and above. However, there appear to be caveats:
It is possible for users to edit text in a rich text box in any supported browser, but ...
-
Can you use File / Save As to save an XML file after your copy table command runs and check the XML for the ID node (or attach it here so I can)? Do all your "Etching" fields in SharePoint have values? I'm wondering if Copy Table is sometimes removing your main data source ID field.
-
Did your command change at all? You didn't rename the ID field or anything, did you? Post your latest template, I'll take another look.