InfoPath Dev

 I did exactly that, and it worked!  So, rules are the same, I just changed the SP field to Rich Text, as well as concurrently changing the InfoPath Form field to a Rich Text Box control - this resolved the wrapping and XHTML code display issue.   Thanks again for clarification Hillary!

Upon further testing, I now realize once I changed those SP field to rich text, it helped with the wrapping, however, now the browser form will not filter the field to display.  I reset the SP field to plain text. And the filter now works again, but I am still getting that wrapping issue. Also, fyi, I have a rule set up that when a ...

 I set the sharepoint list field to rich text, and that solved the wrapping issue - thank you - However, it now adds the html code to the text box like this: <div>4 back 1 stretch , D1 carries F1 will shorten route & for long pass   ,D2 & F2 will come late for drop option. D1 will carry for ...

 Thanks for the response Hillary. Yeah, weird.  I am using IE11, on premise SharePoint 2013. My text box is a plain text box, multiline. In my research, I am seeing there should be an option for word wrap, but do not see it. I see the option to check off multiline, but nothing else. The field also to be noted is a filtered field that is ...

Is there anyone that has an answer to this or some suggestion? I am desperate.   Thank in advance! 

I am using InfoPath 2013 and IE 11 - SharePoint 2013 I have an InfoPath form that has a field for textbox - display options are Multiline. I have a filter set up when one field is chosen, text will be displayed in this textbox.   I am finding that when the text is displayed in the textbox, it is NOT ...

Thank you Hillary. That is very helpful. Changing the first field to value of ID (Display 'title'), and using the Rules worked perfectly! Thanks again! I knew it was something simple.

Thank you Hilary! I created both ways, using the filter and rules on this form. You have no idea how much I appreciate you looking into this - I feel like banging my head against the wall, as it is probably something simple I am missing.

Ok, I would prefer NOT to have rules based on the first field, to be honest with you. In my form, I plan on having multiple Player fields to be filled in, but each of those secondary fields are filtered from the initial Team Field. Pretty straightforward. I was able to get the cascading dropdown to work when I created a third list and then ...

I think I have isolated the problem to the second action item in the Rule - Query using a data connection - for some reason it is returning invalid WHL team from that list. I have the list set up with a lookup column for Team. so, I am not sure why it cannot find and filter by that field.