Browser Forms

Re: Saving is erasing values!!

blue_psychedelic — Fri, 24 Sep 2010 18:55:00 GMT

That's what causes the issue: when people select "send a link" from the item menu in the doc library. For whatever reason, this auto-generated link opens up the the infopah client instead of the browser!

Re: Saving is erasing values!!

ErnestoM — Fri, 24 Sep 2010 12:44:04 GMT

You could email users a link to the library. They'll click the link, go to the library, then click on the document so that it opens in the browser. It's an extra step, but I know of no way to open the form in the browser directly from the link in email.

Re: Saving is erasing values!!

blue_psychedelic — Thu, 23 Sep 2010 14:13:09 GMT

Is there a better way to do this? I am forcing it through the "advanced settings" in the SharePoint Library, but users can still open it in InfoPath when they e-mail a link to the form.

Re: Saving is erasing values!!

ErnestoM — Thu, 23 Sep 2010 13:46:27 GMT

If the value is in the XML when you open in Notepad, then there must be something happening when the form opens in InfoPath.

Anyway, maybe the solution is to disable the form from opening in InfoPath?

Sorry, I'm out of ideas!

Re: Saving is erasing values!!

blue_psychedelic — Thu, 23 Sep 2010 13:30:44 GMT

ErnestoM:

Hello, Let's make sure the process is clear:
1. User submits the form.

2. Workflow adds the Request Number.

3. User reopens the form - when the user reopens, is the Request Number visible in the form? Is the Request Number stored in the xml? (you can download the xml and open it in a text editor to verify)

4. User submits the form and the Request Number is removed. Is this correct? Can you verify step 3?

3: When I open the form from SharePoint, in the browser, the request number appears in the template form field. When I open in the InfoPath client, it isn't there. If I download the form and open it in notepad, the request number IS there.

4: User doesn't submit a second time. I disable submit and force users to save instead. When users save from inside a browser-opened form, the request number remains. If the form opens in the InfoPath client and saves, it disappears from the form, the XML, and the SharePoint Library column.

I thought that it might be caused by how the value is a set (a secondary data connection to the list) but why would it work in the browser, and not in the client?

Thanks for the help!

Re: Saving is erasing values!!

ErnestoM — Mon, 20 Sep 2010 14:23:53 GMT

Hello,

Let's make sure the process is clear:

1. User submits the form.

2. Workflow adds the Request Number.

3. User reopens the form - when the user reopens, is the Request Number visible in the form? Is the Request Number stored in the xml? (you can download the xml and open it in a text editor to verify)

4. User submits the form and the Request Number is removed.

Is this correct? Can you verify step 3?

Saving is erasing values!!

blue_psychedelic — Fri, 17 Sep 2010 13:58:57 GMT

I have a browser-enabled IP 2007 form template running in MOSS 2007. Users add their info, then submit to a SP library. I have a workflow that takes the built-in SP ID column value and stores it in a secondary column in the Library ("Request Number") per end-user request.

I have a data connection to the list that retrieves the value in the Request Number field, and sets it in IP control/field via a rule (So that the request number appears after the user has submitted the form, not before).

I'm running into an issue where users re-open the form a second time (in the infopath client, I can't seem to disable that), add data to fields, then save the form, the request number disappears.

anyone have any clue as to why?