We are using the "declareRecord" RM_Operations step to declare our records.
One issue we've run into is if we've had a multi-value string list and the value has a ' , ' in it it causes an issue on the RM / IER side.
For instance - if I have a value in my multi-value string field (lets call it property A) that is "Client A, LLC."
I use "declareRecord" and use this to declare the document into a record with Property A as one of the parameters I pass.
After the workflow finishes on the RM / IER side my multi-value field (on the RMFPOS side) that is representing property A has a value of "Client A" / "LLC." -- they are two seperate values in its choice list.
Any ideas on how to fix this issue?
This topic has been locked.
1 reply Latest Post - 2013-04-03T16:42:43Z by SystemAdmin
Pinned topic declareRecord RM_Operations step not working correctly
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-04-03T16:42:43Z at 2013-04-03T16:42:43Z by SystemAdmin
SystemAdmin 110000D4XK693 PostsACCEPTED ANSWER
Re: declareRecord RM_Operations step not working correctly2013-04-03T16:42:43Z in response to SystemAdminWe use "," as a delimiter in the multi-value field, and the customer is providing a value containing ",", so we think that is two values there.
The workaround is not using "," in the value.