{"id":45,"date":"2008-12-16T16:38:37","date_gmt":"2008-12-17T00:38:37","guid":{"rendered":"http:\/\/sharepoint.bryanfriedman.com\/index.php\/2008\/12\/16\/multiple-lines-of-text-in-infopathsharepoint\/"},"modified":"2008-12-16T16:38:37","modified_gmt":"2008-12-17T00:38:37","slug":"multiple-lines-of-text-in-infopathsharepoint","status":"publish","type":"post","link":"https:\/\/archive.bryanfriedman.me\/sharepoint\/index.php\/2008\/12\/16\/multiple-lines-of-text-in-infopathsharepoint\/","title":{"rendered":"Multiple Lines of Text in InfoPath\/SharePoint"},"content":{"rendered":"

Scenario: <\/strong>You have built an InfoPath form that you publish to SharePoint to be filled out in a browser-enabled form using Forms Services.  This form includes a simple text field that accepts multiple lines of text and does not explicitly set a maximum number of characters.  When you publish this form to SharePoint and map the fields to Site Columns, this field is mapped to a “single line of text” field, and the default max character length is set to 255<\/em>.  Any characters entered into the field above this length are truncated when the data is entered into the column in SharePoint.<\/em><\/p>\n

I came across this scenario recently and had to do some digging to find out what the issue was and what the best way to solve it was.  <\/p>\n

First, here’s a sample form that will produce this scenario:<\/p>\n

\"image\"<\/a> <\/p>\n

The properties in InfoPath for this text box are as follows:<\/p>\n

 \"image\"<\/a> \"image\"<\/a> <\/p>\n

As mentioned above, publishing this form to a SharePoint Form Library and entering more than 255 characters into this field will result in truncating the contents of the field when it is stored in the column in SharePoint.  This is (probably) not the behavior intended.  One way to handle this is to just limit the length of characters allowed in this field to 255.  By the way, this doesn’t appear to be as easy as clicking the “Limit text box to:” checkbox because, as you can see above, it is grayed out when “Multi-line” is selected.  (You’d have to do some Data Validation using the string-length function — ugly.)  Anyway, if you did this, it would eliminate the possibility of truncating the contents, but of course, you may actually want your users to be able to enter more than 255 characters.  So what’s the solution.<\/p>\n

Well, apparently when publishing an InfoPath form to SharePoint, it automatically maps “string” fields to “single line of text” fields.  In order to map to a “multiple lines of text” field, you have to use an “XHTML” field, which is a “Rich Text” field in InfoPath:<\/p>\n

\"image\"<\/a> <\/p>\n

\"image\"<\/a> \"image\"<\/a> <\/p>\n

Publishing this form and mapping the Rich Text field to the column in SharePoint will result in setting the column to be “multiple lines of text” rather than “single line of text.”  However, there is one small annoyance with this.  Notice the message in the display properties above that says “Only full rich text without embedded images is supported in browser-enabled form templates.”  Annoying.  It means you get this stupid control on your form instead of regular plain text:<\/p>\n

\"image\"<\/a> <\/p>\n

So how can have a regular text field and still map it to a “multiple lines of text” field in SharePoint.  Here’s what I came up with.<\/p>\n

    \n
  1. Create a regular text box (string) control in InfoPath.\n
  2. Create a rich text box (XHTML) field in InfoPath, but don’t display it on the form.\n
  3. Create a rule on the regular text box that sets the value of the rich text box to the current value of the regular text box.\n
  4. Map only the rich text box value to a column in SharePoint.<\/li>\n<\/ol>\n

    You should be able to handle steps one and two based on the screenshots above.  Here are some quick screenshots to show you what I’m talking about for steps three and four.<\/p>\n

    On the regular text box (string) control, create a rule to set the value of the rich text box:<\/p>\n

    \"image\"<\/a> <\/p>\n

    Finally, only map the rich text box value to a column in SharePoint (not the regular text box):<\/p>\n

    \"image\"<\/a> <\/p>\n

    Notice the “plaintext” in parenthesis.  The regular text box field won’t have that listed.  I’m not even entirely sure what it means, but it seems to only show up for XHTML (rich text) fields instead of string fields.<\/p>\n

    This feels like a pretty roundabout way of getting what you want, but then again, the more I work with InfoPath and Forms Services, the more I realize that roundabout ways of getting what you want pretty much seem to be par for the course.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Scenario: You have built an InfoPath form that you publish to SharePoint to be filled out in a browser-enabled form using Forms Services.  This form includes a simple text field that accepts multiple lines of text and does not explicitly set a maximum number of characters.  When you publish this form to SharePoint and map […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-45","post","type-post","status-publish","format-standard","hentry","category-development"],"_links":{"self":[{"href":"https:\/\/archive.bryanfriedman.me\/sharepoint\/index.php\/wp-json\/wp\/v2\/posts\/45","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.bryanfriedman.me\/sharepoint\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.bryanfriedman.me\/sharepoint\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.bryanfriedman.me\/sharepoint\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.bryanfriedman.me\/sharepoint\/index.php\/wp-json\/wp\/v2\/comments?post=45"}],"version-history":[{"count":0,"href":"https:\/\/archive.bryanfriedman.me\/sharepoint\/index.php\/wp-json\/wp\/v2\/posts\/45\/revisions"}],"wp:attachment":[{"href":"https:\/\/archive.bryanfriedman.me\/sharepoint\/index.php\/wp-json\/wp\/v2\/media?parent=45"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.bryanfriedman.me\/sharepoint\/index.php\/wp-json\/wp\/v2\/categories?post=45"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.bryanfriedman.me\/sharepoint\/index.php\/wp-json\/wp\/v2\/tags?post=45"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}