Without more information this is a bit of a guess, but looking at the CDR source code it appears when the CDR’s public record gets created it copies party_a’s and party_b’s userfields into a single shared userfield where party_a and party_b userfield information is separated by a “;” (semi-colon). Something like the following:
party_a.userfield;party_b.userfield
My guess is you are setting the userfield on party_b and party_a’s user field is unset, so when the two are “merged” into a single user field you could get something like what you are seeing. Using the above format, essentially the following:
I’m not really sure. I mean based on the source code, and this documentation I found it appears things are working correctly.
As I said in the previous post. It looks like you are only setting Party B’s userfield so when they are concatenated the field appears to begin with a semicolon.