Hot answers tagged

14

YOu have to check the Allow unlimit length checkbox on the list column's properties page


11

Update: The more structured and concise step-by-step description by Puhan. The answer to this question is the same as answer(s) to question Infopath change Publish Location Update: Though the marked as best and the most upvoted there answers proposing the use UDCX data connection files are not applicable to Infopath Form templates of ...


9

Try editing the SharePoint list settings in the browser. Open the list, go to List Settings, click the field name and select "No" for "Allow multiple selections". Edit after clarification that this is not a list form: The described behavior of the control leads me to believe that the form has initially been created with InfoPath 2007 and the people picker ...


8

I've had a similar problem; SharePoint/InfoPath doesn’t seem to deal with multiple-selection list boxes very well (unless I'm also missing something). The workaround I used w/o code was to create a new hidden field with the default value set to: eval(eval(MultiSelectField[. != ""], 'concat(., ", ")'), "..") where MultiSelectField is your field Tick ...


8

Per that same article, Microsoft has indicated they will support InfoPath 2013 until 2023 and that they are working to provide migration guidance from InfoPath into whatever successor technology or technologies based on Office and/or SharePoint may take its place. If you have a 3-5 year time horizon, I wouldn't rule out InfoPath completely. It would seem ...


7

You should set-up the Item Level Permission for the list or library so only users who created the item can view/edit etc. check out this article that explains how to achieve this in SP2010 Item Level Permission 2010


7

The reason you're seeing this is that your production farm uses Claims AuthN whereas your dev enviroment the classic mode. You should probably make your code handle both scenarios. Here are some details about the claims encoding: http://www.wictorwilen.se/Post/How-Claims-encoding-works-in-SharePoint-2010.aspx


7

While researching this myself, I found a solution that might be a bit better than a substring. You might want to try the following: SPClaimProviderManager manager = SPClaimProviderManager.Local; if (manager != null) { if (SPClaimProviderManager.IsEncodedClaim(encodedString)) username = manager.DecodeClaim(encodedString).Value; else ...


7

Resources Windows 7 OS, InfoPath Designer 2013, Character Map, Notepad Preparation In InfoPath Designer, we want to make sure we can see the panes for Fields and Rules on the left. To show the Fields task pane, click the Show Fields button at the very left of the DATA tab on the ribbon. To show the Rules task pane, click the Manage Rules button at the ...


6

I have a solution (workaround). Only thing you need to compromise on is to replace your option button with check box (but with same functionality as option button). I hope that you have some basic skills with InfoPath rules since my solution is all rules and it is not so simple (but you asked for no code). Step 1: Add two new columns to source list: ...


6

I had the same problem and found out a way to solve it. I saved the form as source files, opened all the files in a text editor (in my case on Visual Studio) and replaced all URLs, used for publishing (actually in 2 files: manifest.xsf and view1.xsl). After publishing it worked fine. Good luck. Regards, Pilan


6

There are a couple reasons it may not be displaying: You're not running the Enterprise edition of SharePoint. This feature requires Forms Services, which are only available in EE. You're looking at a list type that does not support this feature. Basically, any list type that uses a non-standard display for an item, like Calendars, will not have this option ...


6

Concerning the answer with reference to S.Y.M. Wong-A-Ton How to submit the rows of a repeating table in InfoPath to a SharePoint list I managed to succeed in running the code from that article in Infopath 2010 (Sharepoint Online/Office 365) only after I changed CAML template XML file content from given in article: <?xml version="1.0" ...


6

Yes, with People picker field in 2010, you can do it in two steps: Enter the URL to site to query for people/groups In the General Tab, limit the search/selection to specific groups/users. See below


6

When designing the form on the "Page Design" tab select each view and click Properties Then deselect "Show on the View menu when filling out this form" (yes the name of the setting is a bit odd, but that due to how it was displayed in InfoPath 2007)


6

Probably one should use references from Microsoft itself on MS products. So, Microsoft source tells: "Workflow form changed from InfoPath form to aspx form For a workflow based on SharePoint Designer 2013 (WF4) and Windows Azure Workflow, SharePoint creates aspx forms instead of InfoPath forms that were created by SharePoint Designer 2010 (WF3.5) ...


6

Just wanted to share my findings on this issue. I have found that if you resize the Infopath Designer window so that it only covers a quarter of the desktop, the form will then open successfully! You can then maximise the Infopath Window & work on the form as normal. I have tried this on a couple of computers & it definitely allows the form to be ...


5

Go to List Settings. In the General Settings section, pick Form Settings. You can then pick to use either the InfoPath form or the default SharePoint form, and optionally delete the InfoPath form if so desired.


5

You need to tell InfoPath that changes to the field should result in a server round trip. Select the source control. In the ribbon tab Control Tools Properties click Control properties On the Browser Form tab select Always below Postback settings


5

Are you using SharePoint? SharePoint Server 2010 Enterprise edition? If yes, your users do not need to have InfoPath installed on their machine. All is required is to enable InfoPath Form Services in the Central Administration Web site and in the document library settings specify open forms in browser.


5

As a side-off note, Infopath 2003 used JS for code-behind though probably it wouldn't help you in any way since, I guess, you one should understand that Infopath forms are not HTML or web pages, they are XML data to be used by external tools, like for example Sharepoint Server IPFS - Infopath Forms Service, to generate web pages on the basis of XSN Infopath ...


5

The solution is to use the "now()" function instead of "today()" function.


4

My guess is that the error is thrown by a SharePoint field that's is a lookup and it expects an internal ID of list item, not its actual value (visible in the dropdown list). Setting up dynamic drop downs in the out of box SharePoint forms If you get an error that says Only Positive Integers Allowed, you're trying to save a string into a column ...


4

The second review, does it take place within the form or is it a task in a task list? If it is within the form, then wait for a field to be "rejected". If you are doing it as a repeating field so that multiple people can enter, then you can concatenate that field into a hidden field within the form and promote this concatenated field out to your form ...


4

Only reasonable solution for using javascript on InfoPath form would be to create custom page, host InfoPath in webpart and add javascript directly to page. Main issue here is that InfoPath controls ID's are dinamically generated so it is challenge to 'find them' with javascript. A while back I developed one simple solution by using jQuery (and again it was ...


4

I had this same issue and was pulling my hair out. I had to go to Central Admin, Upgrade and Migration, Enable Features on Exiting sites, Check this box "Enable all sites in this installation to use the following set of features:" It then pushed down the features to my site and I then had the InfoPath Button in the customize list group in the ribbon. I'm ...


4

InfoPath Forms Services are part of Enterprise edition. Here you have nice overview Compare SharePoint Editions Also take a look at my answer on licensing requirements for InfoPath forms: SharePoint 2010 Standard and Forms


4

You can use a SharePoint group instead, put your managers in it, and then use something like this to see if the current user is a member: bool IsMember(string groupName) { try { return SPContext.Current.Web.SiteGroups[groupName].ContainsCurrentUser; } catch { return false; } ...


4

You are using the the today() formula, it will return that error you are talking about. For SharePoint fields you have to use now().



Only top voted, non community-wiki answers of a minimum length are eligible