InfoPath Dev

I am working on my first InfoPath form and have a question. I've added & deleted & renamed sections several times as I've worked through this project. I initially had separate sections for each signature required, but after more thorough reading, discovered that all I really need is to have the entire form signed by multiple people (counter signatures). I've ended up with multiple signature groups in the data source and I can't figure out how to delete them. They have locks on them and the delete option is greyed out.

My goal now, is to have the entire form signed and have the digital signatures display in the digital signatures pane as outlined in Microsoft's Tutorial for InfoPath, Lab #10. The code for that uses (signatures1) as the signatures group and I don't have that one anymore. All I see are (signatures2) and (signatures9).

Did you try going to Tools | Form Options | Digital Signatures, and removing the signature areas from there?

I did try that and it would remove one of them but not the other one. I think I finally got it down to just one and the Digitally signed pane shows the correct signature when it's signed.

Now I'm on to the search of trying to figure out why it isn't emailing when I click on submit...

quote:

---

Originally posted by Greg Collins

Did you try going to Tools | Form Options | Digital Signatures, and removing the signature areas from there?

---

Glad you got that part working... be sure to check all your settings for the email, and maybe try creating a test form to see if you can get email working in it, and if so, compare the two to find differences.

URGENT HELP NEEDED

Hi Greg,

I have been playing around with signatures and decided not to use them in a particular form.  The problem is that another form which was based on the shell of the original (with a heck of a lot more programming within) now won't merge the form based on the original because of the dormant signature groups that will not disappear.

I have no signatures enabled in the form options but I now have 2 groups of signatures with 2 sub groups in the form.  I have tried to add groups with the same name to the second form, but it does not match the structure.

The signature groups do not show up in a search of the manifest file.

Regards - Phil

Update,

I have solved the problem.  I had added a couple of attribute fields to the original form and forgotten to add them to the second form. 

BTW the second form needs to have the signature groups/sub groups as per the original otherwise the merge will not happen.

It is still annoying that even with the Digital Signatures option disabled, there are orphan signature groups still residing in the form.

Regard - Phil

Glad to hear you got it working.

You may or may not want to try removing those digisig sections manually. IF you have existing forms that have been saved based on those sections existing, it's probably best to just leave them alone or the existing foms may not open.

I have a similar issue. I have an InfoPath form which no longer uses digital signatures, but has orphan signature groups in the main data source - these cause serialization problems and so i want to remove them. 

In my Main data source I have a signatures1 group with a signatures3 group in it - the folder icon has a little lock symbol on it. All properties are read only. Under Form Options, Digital Signatures i have 'Do Not Enable digital signatures' There is nothing listed in 'Set of signable data'. The xsd has the following (see below). I CAN remove the elements directly from the xsd, but if I try to 'convert main data source', I get 'InfoPath was unable to add or modify the data connection or data source ...

The namespace http://schemas.microsoft.com/office/infopath/2003/myXSD/2009-08-01T23:09:55 is reserved for nodes created by InfoPath

I need a way to remove these old signature elements.

Please help.

<xsd:element name="signatures1">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref="my:signatures3"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name="signatures3">

<xsd:complexType>

<xsd:sequence>

<xsd:any minOccurs="0" maxOccurs="unbounded" namespace="http://www.w3.org/2000/09/xmldsig#" processContents="lax"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

1. Save the Form Files by using File; Save as Source Files

2. Edit the xsd directly and remove the offending parts.

3. go into design mode on the manifest file and use File; Save As to save back to an xsn

see http://office.microsoft.com/en-us/infopath/hp100646591033.aspx#1

Hey Macrel,

Great post.  This fixes the problem, however, my oroginal post was a long time ago and I had moved on.  It's a shame that posts lie unanswered and dormant for so long without the forum overseers attending to them.