Labor Rates To import and update existing records without creating new ones

​@rethavanalphen11,
On the Project Labor Rate screen (PM209900), updates will only occur if the import scenario matches the full business key of the existing record. If even one key field differs, Acumatica will insert a new row.

For Project Labor Rates, the system does not rely on NoteID to determine uniqueness. The record is typically identified by a combination such as:

• Project (if the rate is project-specific)

• Employee

• Labor Item (Inventory ID)

• Effective Date

If your scenario only maps Inventory ID or Employee without matching the Effective Date exactly, the import engine will assume it’s a new rate.

A few things I recommend checking:

1. Confirm in the screen which fields are marked as key (you can inspect this via the GI or by reviewing the DAC structure).

2. In your import scenario, make sure those key fields are mapped and marked as “Key”.

3. Ensure the Effective Date in your source file matches exactly what exists in the system (format and value).

4. Test with a single known record first to confirm it updates before running bulk import.

If the key combination matches perfectly, the system will update the existing rate instead of creating a new one.

Hallo Thank you for the detailed answer.  I need to run the Update the Labor Rates Screen Screen ID PM209900.  The KEY value seems to be PMLabour. RecordID.  On the import Scenario the Key Account  for the Positions I only have the <Key:External> option to map to the PMLaborCostRate.RecordID

The Rate is not Project related only Employee and the only update required is the Labor Item Inventory ID to be removed.