The data entity DirPartyLocationPostalAddressV2Entity can be used to import a location for a party. Upon a POST request through the OData endpoint there is a function that will eventually call the static method "resolveRemittanceAddressLocationId" of the "LogisticsPostalAddressBaseEntity" class. It is used to see if the same address already exists for that party and if it does, it will proceed with an update on that record, rather than inserting a duplicate. This method, however, does not keep into account the BuildingComplement value. This results in an issue where an address is found, where all other fields might be equal to the new address (to be imported), but the BuildingComplement is different, and update that record rather than inserting a new address. Basically, a different address is considered a duplicate and then updated instead of imported, even though the request is a POST request without a LocationId, therefore the request specifically would like to INSERT a new record.

This can be fixed, if one line is added to the a.m. method. Extending the method is not possible as it is called inside the DirPartyLocationPostalAddressV2Entity and the changes would be overwritten. Also, duplicating the whole DirPartyLocationPostalAddressV2Entity and editing some methods there does not work because the model, which has been used to create that entity, is flagged as internal and does not allow any references in duplicated entities. Therefore, Microsoft has to fix this issue.