Dialpeers from different gateways are marked for update

I have imported dialpeer assigned to gateway1, I am now importing dialpers and assigning then to gateway2, I am applying unique columns to prefix and gateway_id, yeti is marking sone of the dialpeers for update instead of for create, why is that assigned to update on a different gateway when i applied unique columns on gateway_id?

it means you already have dialpeers in your system that matching with importing data by selected unique columns.

It was matching the prefix but not the gateway ID.

It was even showing me the ID of the matched record in the O column, I opened it and it was from a different gateway.

Anyways for now I’m good, i wanted to have a test system up and running, and importing a million dialpeers took way too long (low spec test machine), so i ended up importing it directly in the database for now, and i did a update statement to match the prefix with sys.network_prefixes to get the network_prefix_id.