InfoPath Dev

Hello,

i have a "repeating section" (in german: "Wiederholter Abschnitt"). When i
double click on it then the properties are opened of the repeating section.
On "data" in "standardoptions" i can normaly change the name which is also
displayed when the form is in preview-mode. But sometimes are these
fields,which i can change the name, greyed out - so i can´t change it.

This is a screenshot of it:
http://s3.directupload.net/file/d/1481/jqooap5s_jpg.htm

I only want to change the name in contextmenue of the form if i want to
insert or delete another section.
The form is based on a xsd-schema. Do i have to change the schema?

Best regards
Tom

Hello and welcome, Tom:

The only way I have been able to replicate this is if the table is not bound to a section (the control would show a red x in the corner in that case). Can you post the section of your schema that relates to the group/fields your table is bound to?

Hello Hilary,

the table is actually bound to a table. Everything is normal.

 Here is the XSN-File:
http://www.file-upload.net/download-957955/Horchstein.xsn.html

 It has only one repeating section. The underlining XSD is the DDI2.1-Schema - if you know that. What is wrong with the XSD?

 Many thousand thanks to you:)

Best regards
Tom

Looking at your template, here is what I see: the itm repeating section is part of a Choice group, where you have the choice of label (a group) or itm. When itm is bound to a choice group rather than a repeating section, I have the option of customizing the commands for the section. To replicate, grab the Choice group in your schema that hold label and itm and drag it to your form. Find the choice section related to item and when you double click it, you'll see the Choice section properties window opens and you have the option to customize commands.

Is having label or itm as a choice an intentional design decision? If not, you may want to modify your XSD.

Hello Hilary,

then i have to change the XSD many times. . . Oh. . . I have no influence in designing the imported xsd.

But at all i think i must adapt the whole xsd - is it normal that i must do this?

Another question:

When i export a filled in form to a xml-file then all the empty attributes and elements are also exported. In the datasource these attributes and elements have a red dot. I don´t want to export empty attributes or elements. I only wan´t to export attributes and elements which are dragged onto the form. Is there somewhere a option or how can i do this? Or do i also have to change the xsd?

Many thanks

Best regards
Tom

Let's go up a notch and talk about the overall design and what you are trying to do. Your XSD -- was it created in Visual Studio for an existing database, by chance? I ask because I have recently been involved in another post where it seems that the columns that could be null in the database were not marked nillable in the xsd, leaving InfoPath to make them required. See this post for more information: http://www.infopathdev.com/forums/t/8237.aspx. It would make sense that since these fields are considered required, they would be present in the xml whether or not you put them on the form, so you would need to modify your xsd accordingly.

Can you tell me some more about your architecture and what you wish to achieve?

Hello Hilary,

the XSD isn´t created by Visual Studio.

It´s a schema by the DDI-Foundation:
http://ddi-alliance.cvs.sourceforge.net/*checkout*/ddi-alliance/ddi/w3c/Version2-1.xsd?revision=1.10

The DDI-Foundation is:
The Data Documentation Initiative is an international effort to establish a standard for technical documentation describing social science data.

And for this schema i wan´t to make a form so that "normal" users can also create "xml-files". I tried also Altova Stylevision but this tool is also not so good for this schema. The ddi-schema has recursion. And this is making a lot of problems. I don´t need all fields from the ddi-schema.

I think i create a new schema only with the elements and attributes i need. But this makes a lot of work.... Or what would you do? Is there another solution?

Best regards
Tom

A lot depends upon what you wish to do with the data collected from your InfoPath forms. If I was going to start from scratch, I'd just create a new blank form and let InfoPath create the schema as I added fields to the data source. What will you be doing with the filled out forms? Do you need to be able to merge them with XML docs created from the DDI schema? I'm unfamiliar with DDI.

That was a extrem good tip (manually add fields). I think i will do this:)

 The created XML-Files will be inserted into a database. Then published as html or pdf.... Some institutions in germany will change data-information-docs based on ddi - that is the main reason.

So - enough for today.

Many thanks for your help and see you next time.

Good night and a beautiful weekend
Tom 

I'm not sure how you will be storing your xml files, but do be aware of the options for submitting with a secondary data connection in InfoPath. For more information, see these links:

http://theengineroom.provoke.co.nz/archive/2007/09/10/infopath-data-connection-options.aspx
http://office.microsoft.com/en-us/infopath/HP012304861033.aspx?pid=CH100598301033#1

Just in case you need to be basing your form off an existing database -- I'd hate for you to get it all designed and pretty and hit a wall on Submit.

-- a good weekend to you as well!