Details
-
Type: Bug
-
Status: Done/Fixed
-
Priority: Trivial
-
Resolution: Fixed/Completed
-
Affects Version/s: 4.4.0
-
Fix Version/s: 4.4.0
-
Component/s: None
-
Labels:None
Description
The API doesn't add custom separators when a single integer is passed in on preferred communication method.
I'm wondering if this should be marked in the xml in some way & then applied at the initial API layer. One to discuss with Colemanw
Attachments
Issue Links
- is supplemented by
-
CRM-13123 Handle value-separated fields at the dao level
- Done/Fixed