General

Re: Submit Rule Problems

Patrick Halstead — Fri, 16 Feb 2007 08:48:46 GMT

Hi Vassago,
I like your solution!

Re: Submit Rule Problems

Vassago — Fri, 16 Feb 2007 02:51:02 GMT

In case anyone was wondering, I found a way around this problem. I set up the default view of my ForName location to only show forms submitted by [me]. Then I set rules on open of my form to only submit to the forname location if the getname data connection doesn't retrieve the user's name (i.e., they've never opened the form before, so never sumitted to getname). This will mean everyone who opens the form will have at least one form entered into ForName, but it's better than nothing and seems to be working perfectly on initial testing.

Re: Submit Rule Problems

Vassago — Thu, 15 Feb 2007 02:31:42 GMT

Unfortunately, I can't make purchasing decisions for my company, but I appreciate the offer. It seems to be happening actually on either submit and not just the first time now. I've tried having it submit via script and rules, same thing. Is there a problem one form in infopath submitting to more than one sharepoint library? When I only submit to one library, I recieve no errors.

Re: Submit Rule Problems

Patrick Halstead — Fri, 09 Feb 2007 23:02:27 GMT

Hi again,
We'd have to look at the solution. This sounds like it is solution specific. I.e. there's some code in the form that is doing something special. If not, it's hard to imagine what is causing this. We could look into it for you if you want to buy a 4 hour support pack. Cheers!

Re: Submit Rule Problems

Vassago — Fri, 09 Feb 2007 21:25:47 GMT

Thanks for the reply Patrick.

I tried waiting more than ten minutes and USERB is still recieving the error. I figured it must be some lock happening that is not allowing it to overwrite the SubmitForName location. The weird thing is that it works the second time for USERB, no matter how much time they wait. They can do it within a minute and it'll submit the second time. Weird huh? By my description, does it sound like it may be locking the First Submit in some way that will only keep it locked the first time?

Re: Submit Rule Problems

Patrick Halstead — Fri, 09 Feb 2007 04:36:55 GMT

Hi Vassago,
This is probably the SharePoint 10-minute locking going on. The locking behavior will make the form read-only to other users. Did you correctly close the form from the first machine before running it from the second machine, or is InfoPath still running? Try closing InfoPath from the first machine and then do the UserB and see if it's different. If it's still happening it could be an issue where your code is not releasing a lock but that's less likely. In any case, if the first thing didn't work, try waiting 10 minutes and 1 second after you closed InfoPath and then try opening.
Good luck!

Submit Rule Problems

Vassago — Fri, 09 Feb 2007 03:44:29 GMT

Hello all,

I have an infopath form I have designed with a field named "Submitted By". I have set a rule on load to use a data connection called "SubmitForName" to submit the form to a Sharepoint Library named "ForName", where is overrides the form on each submission. Once that is complete, another action recieves the "Modified By" field from another data connection named "GetName" that reads the Library "ForName" to obtain the name of the user who submitted the form. This seems to work fine for USERA as many times as they open it, the name will populate. The problem is when USERB opens the form, they recieve the following error the first time it tries to submit only, regardless if the form already exists or not:

Infopath cannot submit the form.
An error occurred while the form was being submitted.
The form cannot be submitted to the following location: <SITE>
The site may be offline, read-only, or otherwise unavailable.
Unspecified error.

The funny thing is, they can then open the form as many times as they choose without any errors and their name populates fine. THEN, if that wasn't enough, now USERA cannot open the form without first recieving the same error the first time. Then the process repeats itself.

So it seems to error out the first time for each user who is not opening it for at least the second time consecutively. This error also seems to happen whether it's a rule onload or attached to a button/field.

Does anyone have any ideas or a better way to accoplish what I want?

Thanks!

Vassago