InfoPath Dev

I have two lists of multiple-selection list boxes, the values of first list would be used to filter and populate the second list. the behavior of them are acceptable until when one day when I bind the second list 's Value and Dsplay Name to different fields of a data connection. For example, we have product category in the first ...

Thanks, some colleague of mine read your post and thought the Savable field and the rules somehow could cause the existing validation to be bypassed. My understanding is that the validation rules are *additional rules* on top of the requirements at the field level, if we are not meeting the requirment we set up at field level, the validation ...

Just want to clarify this, that you made all the fields *not required* FIRST then you add a Validation rule to EVERY required field and add a condition based on the Savable field. Is my understanding correct?

Kind of, the Description rich text data "copied over" from the secondary data source is for display only, no need to be persisted in the Proposal form. Thanks

Hi, Jim and Jimmy: Thanks for the replies. The Secondary Data Connection used by the Default Value Formula is a connection to a SharePoint Library. Basically we have two forms one called Project, one form called Proposal, there are an ID field and a Description field(Rich Text) on the Project form, and on the Proposal ...

I found this old thread of this forum, which seemed to be a possible solution, but it isn't: http://www.infopathdev.com/blogs/greg/archive/2005/06/13/Display-Rich-Content-in-an-Expression-Box.aspx  I opened the .XSN file and checked the View1.xsl file inside, the control is already using ...

Recently I ran into an issue with InfoPath form, I was displaying Rich Text data from an Second Data Connection(to a SharePoint library) in a Rich Text control(by setting its Default Value using a formula), they were rendered as plain text, all the formatting such as bullets, coloring, and font was lost.   And the Rich Text data ...