@aparimala thank you for sharing the inputs here. Redirecting this to the product team to check the possibility.

@aparimala Can I know how the First and Last name fields are populated? 

Are they populated in Bulk using Rules or Jobs, or are they populated manually from the C360?

In the bulk options if all the three fields are mapped, the Name field would automatically concatenate the strings from First and Last name.

We are also working on improving the experience to bring the behavior across all input areas.

Thank you

Preethi

We are bulk updating first name and last name and full name for contacts from SFDC to GS using SFDC Connector jobs.

With the connector job - the update is one to one mapping for all the 3 fields (first, last, full names) to the fields in GS Person record.

We also have records that come from other sources through rules engine (upsert action). Person section is where our CSMs go to update/add/enrich a record.

When updating a record (irrespective of the source), if first name or last name is updated - the full name should reflect this change or vice versa. 

Right now my experience is that you have to update all the three fields independently which is redundant and causes gaps when using Person records for JO programs as one of the use cases.

Hi @aparimala 

You’ve been heard, the Person Admin section is planned for a revamp on our near term roadmap. We will be mindful of accommodating multiple changes in terms of selecting fields by the admins.

Thanks,

Shilpa

Chiming in here.

The Person model is pretty kludgey today. When adding a new Person, users just type in the “Name” field, and often skip over the FirstName and LastName fields. And we aren’t even able to set the FirstName and LastName as required. So we end up with a lot of garbage data.

In some instances, we even sync back the Person records to Salesforce. And when we encounter records with a missing FirstName or LastName, our sync jobs fail. 

This post hasn’t been updated in 2+ years, when @Shilpa Gumnur from the product team stated that a revamp was coming in the near-term. Seems like either this wasn’t considered for the near-term roadmap changes, or that those changes were more long-term.

Adding on to Jordan’s post.

It is awesome that GS finally came out with the ability to make Name, F Name, and L Name mandatory. However, this is not easily done as in order to do so you have to have a value for all current records. Making it a long drawn out process to figure out what you enter.

It’d be nice to be able to just make these fields mandatory on the UI side but still let us enter with rules without.