Tag Info

When you published the form, it would've prompted you to save it to your hard drive. Simply open InfoPath Designer, and edit the saved form. When you are done modifying it, publish it again and it will update the previously published form.

I think the problem is caused by how InfoPath works internally. It looks like numbers are casted between decimals and doubles and some precision is lost. For example the first number will probably something like 0.22449999999 instead of the 0.2245 it should be and therefor it will be rounded down instead of up.
So I ended up rounding it twice, first on 7 ...

For users that do not have the InfoPath client installed, you'll want to create a Browser Enabled InfoPath form.
This will let your external users open and complete the form using their web browser.
For further details, please refer here: ...

Any answers to this question are going to be largely opinion-based, so please keep that in mind. That said, it's a question most SharePoint admins will face eventually - you have a system built in SharePoint that is USED by a large audience, but is OWNED or MAINTAINED by one or more smaller audiences.
In most cases, I place both the form template and the ...

What you're describing is a Filtered Lookup Column, and it's a feature that SharePoint doesn't support OOTB. There ARE, however, several solutions available for creating your own.
If you want the filtered lookup functionality available from within the normal list interface, you'll want to look into a custom solution like this one on Codeplex. This ...

You can create an Info-path form but only using form based approach, it allows you to add code using visual studio, Also make sure when you install MS office you choose the option of Office development tools in Visual Studio. Then only you will get the option in info-path for coding.
You can also check the below link.
...

OOTB SharePoint does not provide this functionality but there are several third party tools available for this.
This link provides an Open Source solution to requirement in question.
It will basically create a custom column which will allow to upload picture from local drive.

Here is a very nice link explaining in detail regarding the requirement in questions.
Following are main steps:
1) Add new receive data connection.
2) Select List from which you want to fetch data.
3) Select all additional fields you want to be displayed on form.
4) Insert a calculated column on form.
5)Click on Advanced View for this field.
6) Select ...

You need to add the logic to set the boolean field just before the submit rule on the button, and have the formatting rule on the button to hide it when that boolean field == true.
If you add this logic to the field after the submitting rule, it will not be saved with the form, and next time users open the form it won't be hidden as the rule to hide it came ...

Have you changed submit option in info path to your new location (production) ? If you want to publish directly to SharePoint library or list then in this blog all the steps are mentioned and if you are trying to publish it to the content type then you can follow the instruction given in this link,

My personal experience--you can easily manage multiple list items in the infoPath List template (meaning you can have your repeating field not overwrite itself each time a user inserts the field (needs secondary XML). However, I am switching to the infoPath Library template form because I need digital signatures and it appears the the list template doesn't ...

You will need to promote those columns by re-publishing the form. As you step through the wizard for publishing your infopath form a dialog appears where you can choose which columns you want to appear as promoted columns on the SharePoint list.
You can see the steps here in this blog post: ...

You should be able to accomplish this by creating a new view in Infopath. essentially you are creating two separate forms that can function differently and show different fields.
You do this by selecting the Page Design ribbon and then click on the New View option on the left. You can cut and paste your original form into the new view for a quick start on ...

Previously, an employee's name was entered into a people picker, which populated an employee ID field. The Employee ID field had a rule which set the query value from that, queried a data connection and was done. The Employee name field's default value was set to as the value of name = PreferredName, email field default value as name = WorkEmail, etc, up a ...

The issue is the way that SharePoint infopath forms work is the data is stored in the infopath xml file itself and any promoted columns will also store the data in form libray (the content database) as column data. So since you are updating the database directly, you are only changing what is shown in the sharepoint column on a view and not what is actually ...

They are giving out mixed messages at Redmond. Some of their blogs don't give any real clue (as Per Tomasz' post above) yet they have given demos of something called Forms on Sharepoint Lists (FoSL). This appears to be the same form technology as used in the current Access 2013.
Have a look about halfway through this video for a very brief demo (full of ...

For me there's no real replacement for InfoPath right now...
Please find official post on the Microsoft site:
http://blogs.office.com/2014/01/31/update-on-infopath-and-sharepoint-forms/
As you can see in case of complex forms Microsoft still suggest to use InfoPath. Also please remember that InfoPath will be supported for next 8 years. And in terms of IT ...

Just went through the following link Update on InfoPath and SharePoint Forms
I might be a bit late to the party but Microsoft SharePoint team is also taking recommendation from SharePoint Dev/User community here

This is an old post, but I don't see a resolution provided, so I'll share a solution that fix this issue for us. We were getting the same error as the above user,
but were instructed by MS to Disable the loopback check on the server and this issue went away.
Hope this helps someone else.

I think you have two options here.
You can turn on Version History for this list. I won't show it like you have above, but it will collect the data.
You can create a new multiple lines column and append the new modified information to that column.

Have you tried this idea?
1) The first thing you need to do is disable the save/save as buttons, and instead of using those on your form, use a custom submit button (no code) by following my blog entry: Auto-Generating Filenames for InfoPath Forms.
2) Then, add a 2nd button that does the same thing, but make it so
that this either uses a separate ...