whew! I figured it out, what a pian in the neck this does not work easier. After writing the post I remembered an old post related to cascading fields. I remember that the data sources had to be replicated. I dont remember the reason, but I went an added my lookup data source a second time. I also used an xml file to insert a newline. With my multiple select lookup field I have a button, so once I am done selecting my values, it will run a rule to update a text field and submit my form. Keep in mind this is a customized sharepoint form. the rule is to set a field value and looks like this
XPath:
substring-after(xdMath:Eval(xdMath:Eval(xdXDocument:GetDOM("Region1")/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW/d:Title[. = xdXDocument:get-DOM()/dfs:myFields/dfs:dataFields/my:SharePointListItem_RW/my:Region/Value], 'concat(xdXDocument:GetDOM("characters")/characters/@crlfb, .)'), ".."), xdXDocument:GetDOM("characters")/characters/@crlfb)
rule:
substring-after(eval(eval(Title[ID = Value], 'concat(xdXDocument:GetDOM("characters")/characters/@crlfb, .)'), ".."), @crlfb)
I am not going to explain the double eval. there are already many post on this site for that. toi get my scenario to work this was the key:
Title[ID = Value]
Title in my second (replicated) data source. and Title is the title field used in the look up, then I just compared the ID to the value of the multiple select. on button click each value display name is written with a semi-colon each on a new line.