Pb with an automation

First thought is your trigger, it sounds like you’re using “When Record is created”. Unless you’re adding information via a form, that’s a tricky trigger because the record is created when you click the + in the data layer (and inherently no information is contained at the moment of creation). I would add a checkbox field and change the trigger to “When condition = checked” and see if it works then.

Another thought is whether you’re using Create a Record or Update a Record as your automation action. If you’re creating a record in Contact Behavior, it needs to be a Create action, not an Update action. 

For the trigger timing, you could also use "When record matches conditions" where CompleteName is not empty. This ensures the formula has calculated before running, without needing an extra checkbox field.

And yes, definitely use Create record action, not Update, since no Contact Behavior record exists yet for new contacts.

I briefly considered this and the issue is that if they are typing in data (as opposed to copy/paste) then the Complete name field will be filled in as they type in one of the name fields. 

There’s always script delays, or perhaps you wrap the Complete Name formula with an IF statement that leaves it blank until both fields have data, but these are more complicated solutions for someone just getting started with automations. 

Does this look right?  If so I’ve set it up here for you to check out

The automation triggers when a record is created in Contact, and creates a new record in Contact Behaviour, linked to the original contact record:

As the records are already linked, there’s no need to create a text field in Contact Behavior to store the name, we’d add a lookup field to pull over any data that we wanted or use the linked field value if that worked, does that make sense?

Hi,

Of course you might have special reasons to do it in such way, but usually, when my records in two tables have strong one to one relationship, I found that the best way to manage it to avoid overengineering, is to put them in the same table and use views to distinguish different sets of columns.