CSV import/export problem with GUIDs

[mse]

I have a CSV file that is properly set up and it imports just fine in EA. I also notified that updates to the requirements once imported also works. Here is the problem. I notice in the project properties, that  the GUID is different from the one in the .csv file. Despite this difference, EA recognizes the requirement and updates it. How is that even possible? For example, I have a row with a GUID in the original file like:

{0D27BCD8-3538-46E6-BB30-D135A3567CDB}

Yet in EA, for that item, the following is showing:

{3CCA78B8-2E19-4a30-8F05-810546BE9BC8}

And despite that difference, EA still updates that item if I change some text. That is what I want, but I don't understand why the GUIDs are suddenly different.

[Geert Bellekens]

The guid is what EA uses to know which element to update, so it is technically not possible for it to update an existing element with another guid.

Are you sure you are looking at the correct spot in EA?

Geert

[mse]

That is the strange thing about all of this. EA is somehow holding on to the original GUID that was in the first import, but then creating its own and using it. I noticed this because when I export the package using CSV export, the column for GUID has different GUIDs for all of them. If I export my original CSV however, all items are "updated" even though the GUIDs do not match. It's almost as if this were a bug of some sorts.

The workaround I suppose is to export the package, and import it in the original tool where I had done the CSV export. The GUIDs in the other tool would be updated, and from then on, they would be the same, but that seems like a strange workflow.