On Tuesday, December 30, 2014 at 7:00:25 AM UTC-5, Vincent Bastos wrote: > > Hi, > > I have a current requirement for the party field to have a first name and > a last name. This is going to be especially useful when we send out email > to customers. AFAIK in English and French speaking countries most people > are addressed to using their first name. > > A few software solutions I have seen around usually separate the name as 2 > fields, but I suppose this probably depends if the business is dealing with > people as customers or business as customers. > > I would be interested to hear whether other people have had similar > requirements/use cases to have a first name and last name and what their > solutions have been? > > I know that in Salesforce for example, there are 2 types of "Account" > "objects" ( in Tryton this translates to Party models ): a "Person Account" > and a "Business Account". The business account only has a name field, but > the Person account has a "composite" name field made up of 2 fields ( first > name and last name ). > > Also all the most popular web based accounting packages have first name > and last name field. > > I am not saying that they are correct, but I curious to hear people's > thoughts around this topic. > > Cheers, >
In GNU Health, they have boolean fields on the party to select : - is_person, - is_patient - is_pharmacy - is_institution (e.g. hospital, doctor's office) They then add a "Lastname" field that holds the surname for the parties with is_person=True We have extended this model a little by adding firstname and middlename fields that are invisible for all parties that are not is_person. We then make the name field readonly when you check "is_person" and generate a name as *surname, firstname m.* or *surname, firstname* if there's no middlename.
