parse last name
Answered
I have some customers with a space in their last name(s), but the system automatically parses everything before the final space in the full name as part of the ctfirstname variable/field.
The profile just has one field for full name, so I can't choose which goes where. (In contrast, when merging duplicates, I can choose what goes in as a first name and what goes in as a last name).
How do I get the system to treat a last name with a space in it as one last name in the customer profile?
(ie. Will Van Atta: FName: Will, LName: Van Atta)
The same question
I have developers looking into this and will advise when we have an update.
I have developers looking into this and will advise when we have an update.
Developer advised we had something similar with common Spanish last names and created a list of them, to have them parse properly. They have added Van, but if you have any other common ones they can add those too.
Developer advised we had something similar with common Spanish last names and created a list of them, to have them parse properly. They have added Van, but if you have any other common ones they can add those too.
Thanks, Gabrielle. Is that also to say that there's no manual way to do something like that?
My workaround is to intentionally create a duplicate for the customer, then use the Merge Utility to parse the name correctly. It's a bit cumbersome.
Thanks, Gabrielle. Is that also to say that there's no manual way to do something like that?
My workaround is to intentionally create a duplicate for the customer, then use the Merge Utility to parse the name correctly. It's a bit cumbersome.
Correct our developer would need to add them to the list in our code.
Correct our developer would need to add them to the list in our code.
I don't mean to have it parse automatically, but just to be able to define the ctflname and ctlname fields individually.
I don't mean to have it parse automatically, but just to be able to define the ctflname and ctlname fields individually.
Developer has advised no there is currently no way to do it manually except the work around that you were already doing.
Developer has advised no there is currently no way to do it manually except the work around that you were already doing.
Replies have been locked on this page!