01-Sep-2026 — create new members from Insight Hub when firstName is Skip ref #375

build 872 — commit bb44e49

What's new

An Insight Hub bulk load of a new member could fail with first name required, even when the uploaded row had a first name. Skip on first name is meant to keep a local value on an existing member. On a new member there was nothing to keep, so the name stayed empty and the save was rejected. Upload History then showed an error while Members Uploaded still showed the name from the file. New members now take first and last name from the file, and Skip still protects existing members.

At a glance

• A new member from Insight Hub is created with first and last name from the uploaded row, even when those fields are set to Skip
• Skip on an existing member still keeps the local value
• Email and mobile on a new member also take the inbound value when those fields are Skip
• Member Sync Policy help text now says Skip keeps the local value on an existing member, and a new member still takes the inbound value as the starting local value