Getting Locations to actually map when you import Assets into ACC (two-pass pattern)

[josebaqueror]

If you have tried bulk-importing Assets into ACC and watched the Location come in blank, sharing what fixed it for us.

The Location on an asset is a reference to a node in the project's Locations (LBS) tree. The import only binds it if the value in your file resolves to an existing location, exactly. So the order of operations matters:

1) Build (or import) the Locations tree FIRST, before the assets. If the location does not exist yet at import time, the asset row has nothing to bind to and you get a blank.

2) Match the path exactly. Use the full location path the way ACC stores it (parent then child), with the same names and the same delimiter the template expects. A trailing space, a different separator, or "Level 1" vs "L1" is enough to make it fall through to blank.

3) Import the assets in a second pass, with the Location column populated using those exact paths, and map that column to Location in the import mapping step.

4) Spot-check a handful afterward. If only a subset came in blank, it is almost always a name or path mismatch on those specific nodes, not the whole import.

Doing it as two passes (locations, then assets) instead of one combined file is what made it deterministic for us instead of hit-or-miss.

How is everyone else handling this at scale: are you building the LBS by hand, or importing it too?