InfoPath Dev

Hi,

I have created a custom button with the 'is blank' & 'is not blank' rules mentioned in various posts on the internet.

When submitting the form for the first time it creates the new form which is visiable within the forms library.

If you reopen that form from within the forms library and change anything it does not update the fields to reflect this.

The submit button has the following rules configured using Rules & Custom Code.

Rule 1

Edit (filename is not blank)

Action 1: Submit to data connection

Action 2: Close Form

Rule 2

Submit (filename is blank)

Action 1:Set a Fileds Value concat(CR_Number_Short_Description, today())

Action 2: Submit to data connection

Action 3: Close Form

The button uses a data connection to the forms library with 'Allow overwrite if file exists'.

Can anyone tell what I am doing wrong here please this is driving me mad for the last three weeks.

Regards

GF

And the field you are setting is the same field that is used for the Submit connection in your form? Attach a copy to a reply in the options tab if you want and I can take a quick look and see if I see what may be going awry.

Hi,

Thanks for your reply, really appreciate your help I am rapidly turning grey trying to solve this issue.

I have attached a copy of my form albeit it may have changed config since posted my original issue but you will no doubt see what I am trying to do.

In it's current config it is now creating forms in the form library but I cannot edit the existing form without it creating a new form in the forms library.

Further along the line I am also usign a Nintex Workflow that creates a calendar entry in a SharePoint Calendar list when the form is submitted and again the item is being created in the calendar but any changes are not being saved.

Thanks

GF

Hi Hilary,

Any update please?

Thx

GF

Your Submit data connection uses an expression to create the file name. I'm imagining the result of this formula is different every time, which is why the file isn't overwriting. You have a second submit connection that uses just a single field for submitting -- When you resubmit a previously submitted form, what is the difference in the name you get? Because if the names aren't the same, you can't overwrite.

I am using the SubmitMain data connection.

I need to be able update any field in the form and have that saved back to the same form in the form library.

i.e if I put the value 'C00000000' in field 'CR Number & Service Name' and then re-open the form and change this field to 'C111111111111111' I want this to change within the forms library and calendar list library.

I have read posts regarding using a hidden field to achieve this so I created a text box called filename, but I then have problems creating the 'is blank' & 'is not blank' rules for this.

Thanks

GF

I cannot think of a code-free way you'll be able to change the name of your file and overwrite an existing file. I'd suggest you use a different naming convention and promote your CR Number to your list instead. If you want to use the built in submit functionality of InfoPath to overwrite an existing file in the library, your file name must stay consistent. If you are changing the 'CR Number & Service Name' and that is part of your file name, you will always get a new file.

So for instance if a user submits a form and the 'CR Number & Service Name' is incorrect they cannot re-open the form and edit this without creating a new form in the forms library?

It's seems like too much of a restriction to be true, surely you can updated the existing form without haing to create a new form.

I thought using a combination of the 'is blank' & 'is not blank' rules overcame this?

I am obviously failing to explain myself clearly.

If you wish to use the "overwrite existing" option on a SharePoint library submit connection, do not use fields whose values could change for the filename. Use something that will not change - for example, you could have a filename field that uses the username function and concatenates it with the now function - you'd have filenames like "jsmith - 20110201T10:23:45.xml". Since jsmith is unlikely to submit two forms at the same second, you have unique filenames. Since the function is in a field and not in the formula editor for the data connection, the "now" value won't get updated each submit.

I don't have any idea how using a combination of rules could overcome the fact that in order to overwrite an existing file in a SharePoint submit connection, the name you are using for the file needs to remain consistent. You can change other data in the form without an issue. If other data needs to be exposed in the library, use promoted properties.