Hi, I am working on an inbound .CSV to HRImport integration to load new hires from a vendor recruitment system.

Originally replied by Brenda Sutton on Aug 28, 2026, 1:27 PM.

Happy Friday @Leigh Hayward​ , best practice would be to populate LoginId explicitly in the HR Import rather than rely on the Login Algorithm client property, since that algorithm isn’t applied to HR Import new hires. If generating First.Last, make sure the design also handles collisions (for example, two employees named John Smith). Ideally, agree with the client on a deterministic uniqueness convention such as john.smith2 or john.smith01 before building the mapping. The HR Import specification supports LoginId as an Employee field.

Originally replied by Leigh Hayward on Aug 31, 2026, 6:38 AM.

Thanks @Brenda Sutton​ , I will try and figure out a way to check for duplicate log in IDs in IS.

btw, did you have any joy changing my name to Leigh Peabody in Community?

Originally replied by Brenda Sutton on Sep 1, 2026, 11:48 AM.

@Leigh Hayward​, I finally figured out that you had 2 contact records in Salesforce. Sterling helped submit a ticket to get the one with Hayward deleted. Hopefully that will resolve the issue. You may want to save anything that has the Hayward tagged to it just in case you can no longer see it.