InfoPath Dev

I have the following for save/submit buttons using InfoPath 2007 web based form on SharePoint:

Field "Increment" - Whole Number - default 0

Note: save button always visible

1) Submit is hidden because of Conditional Format: Increment "is equal" 0 - Hide this control
2) Save button is clicked resulting in submit becoming visible because of Set field's value: Increment=1
3) Submit is clicked - for only one time - hiding Submit because of Set field's value: Increment=0.

Unfortunately, after the save button is click again, submit is visible. I'd like to know how to always hide submit button after step 3? Can it be done?

Any help would greatly be appreciated.

are these buttons, ones you added? If yes, I went to one button and added a set of rules.

I started with a hidden field called FileName. On open this field is blank, On button click I do 3 actions:

1. Set this fields value, to my concat string

2. Submit using my submit data connection

3. Close the form: No Prompt

If FileName is not blank, then I already submitted the form, and I take these 2 actions:

1. Submit using the data connection

2. Close the form: No Prompt

Initially I tried using two buttons but was not happy with the results. Having similar issues to what you explained.

Let me know if you have any questions

Thanks for the quick reply jaxkookie. Let me be a little more specific.

Two buttons (save/submit) are setup because users sometimes do not want to submit form just yet (only saving). The initial save will create form in library and once clicked submit is visible. Submit has:
1. Set field's value
2. Submit email data connection - emails to user and our group
3. Close form

Then and only then I want submit to always stay hidden because of "emails" each time generated. I tried all 'math' functions even concat with no luck. I tried field "increment" + 1 as a rule thinking I could make submit conditional format as greater than or equal to a number but that didn't work. Any suggestions?

I am not sure I understand why the need for submit/saved buttons, but I believe I understand what you are trying to accomplish. Can you attach a sample of what you have and let me look thru? I may be able to see what your missing

Thanks Larry,

That would be great! This is what I recently have for you to look at.

Please let me know if you need anything else. Thanks again.

It may be easier to see the form, but it looks like you are incrementing your field. How about trying to just do an On/Off. set the field value to 1 or 0. I am not sure the reason to increment to 10, but you still may be able to achieve this. i would like to solve for you button issue first. If you can simplfy it to be an on off state maybe using another hidden field, then when you click the button you can set the field value to 1 or 0 base on the scenario. you may then be able to increment later as a secondary result.

Sorry Larry, I realized that it must be a little confusing with the screen shot so I have stripped out the proprietary stuff and attached the .xml.

The reason to increment by 10 was if the user was still not ready to Submit, they can keep saving 10 times before the the submit button gets hidden. I tried Boolean, similar to the 1 and 0 you suggested and it didn't work as I wanted.

Hope it is clearer now. 

Sorry it has taken so long to get back. I have had to replicate the form from what I could make of it in design. Could you explain where you are having your issue again?

I think I understand what you want, it is not as much an issue as it is logic. When you click you submit, set the value to 10 or 11, not 0. this should get you what you want.

I have added another field and tweaked the rules. this sample will allow you to count all save clicks, and hide final submission after 1 click

Yep! UDAMAN! That did it but the set field's value: increment2 = 10 given in the submit button didn't save when closing and opening again. Why didn't that value save so the Submit doesn't show up ever after the one submit? My submit button was visible

I replicated this and published it out. what I found out is the final submit must not be converted to a submit. if you keep it Rules or rules and code you can add three rules when it is clicked.

1. increment = 10

2. submit data, using you "Main Submit" or what ever you named it.

3. Close the form

these actions keept he fields values and the button stayed hidded.

OH MAN! That was it! Thank you so much for all your help! I have finally finished up and will be presenting to my team the "New Better Form".

I just am afraid of incorporating this new form to the old form because there has been so many changes that when trying to open up old form, it will not be backward compatible. Wish me luck!

Did you know you can use Preview to find out if your old data will open in your new form? Check it before you publish.

Here's a blog post on that.

Thanks Hilary for that information but my situation is much more difficult. When I originally published the production form I used "Document Library" instead of "Site Content Type (advanced). So now, not only have there been major changes but how do I correctly set the environments?