Newbie Questions

Re: Sharepoint form not keeping formatting after Infopath modification

ErnestoM — Tue, 29 Jan 2013 14:11:04 GMT

Did you add these fields as columns on the SharePoint list, or did you add them directly to the form template?

Typically, for SharePoint list forms, you add the columns first to the list, then design the template to add them as needed to the view. (not the other way around)

Re: Sharepoint form not keeping formatting after Infopath modification

dahlstroem — Tue, 29 Jan 2013 13:54:55 GMT

Ok, thanks - here's the XSN of a brand-new list. I noticed that when I open it in InfoPath, the original formatting of the form is already gone.

cheers.

Re: Sharepoint form not keeping formatting after Infopath modification

ErnestoM — Tue, 29 Jan 2013 13:46:46 GMT

To get the form from the server:

* Click the 'edit form'-button in Sharepoint -> "Open this SharePoint list form in Microsoft InfoPath?" -> Yes -> InfoPath

Then save this XSN locally.

Thanks!

Re: Sharepoint form not keeping formatting after Infopath modification

dahlstroem — Tue, 29 Jan 2013 13:25:50 GMT

Hi,

here's the local copy of the modified XSN. I'm not really sure on how to get the original version of the form saved

on the SharePoint server. Please advise.

It's actually just a basic Sharepoint "Issue Tracking"-list, with a few fields modified to suit company needs.

Cheers,

//rd

[edit]

I just checked the site through SharePoint Designer, and could find the XSN-file in the Issue Tracker-list that I created.

When I created a new similar list to use as reference, the XSN-file wasn't there to begin with. Could Office365 be using

some sort of template from the cloud, and when modified can no longer access some kind of required site?

[/edit]

Re: Sharepoint form not keeping formatting after Infopath modification

ErnestoM — Tue, 29 Jan 2013 13:14:57 GMT

Could you save the XSN locally and attach it to your next forum post? You can attach via the Options tab.

Actually, it would be great if you could:

(a) download the current XSN, save it locally, and attach it here

(b) make changes to the XSN, save it locally, and attach it here.

That would give us a chance to compare the forms and look for any potential issues.

Thanks!

Re: Sharepoint form not keeping formatting after Infopath modification

dahlstroem — Tue, 29 Jan 2013 11:25:11 GMT

Hi, thanks for the answer.

The modification process has been as follows:

* Click the 'edit form'-button in Sharepoint -> "Open this SharePoint list form in Microsoft InfoPath?" -> Yes -> InfoPath

* Make adjustments.

* Quick publish to server. -> "Your form template was published successfully."

I assume that I'm in design mode, and that I'm modifying the live-version of the form template. I haven't

made a local offline copy of the file before publishing it.

As for the versioning, editing and publishing makes changes to the server copy, and increases the version number by 0.0.0.1

when re-opening it from the server.

Best regards,

//rd

Re: Sharepoint form not keeping formatting after Infopath modification

ErnestoM — Mon, 28 Jan 2013 13:37:54 GMT

I'm not sure what process you're using here, so perhaps we should check.

Are you modifying the XSN (form template) and republishing it? (to a list?)

And then when you open the form it shows the previous version of the form?

I would definitely check the version numbers of the form. (Advanced Form Options)

1. Open the form in Design mode and make changes. Note the version number!

2. Save and Publish.

3. Download the form from the server - are the changes there? Check the version number. Is it higher than in #1?

Sharepoint form not keeping formatting after Infopath modification

dahlstroem — Mon, 28 Jan 2013 10:29:10 GMT

Hi all,

I'm having a problem with a form, and mostly its formatting. The problem occurred when I tried to modify one of the

attributes of the form through Infopath, and the formatting of the original form disappeared completely.

This first picture illustrates the form in its original shape, and the second image the form after a field has been added to it:

The Sharepoint installation is on Office365. Is there some sort of incompatibility with this that could be causing the problem,

or is there another solution?

Best regards,

//rd