Depot import

Owner: Clara Rossi · Epic: ENG-1710 · Shipped: Friday 25 September · Shaped in Emargen as "Vossberg depot import"

Why

Vossberg has 60 depots and we had 41, made by hand with codes that didn't match Okta's. A customer with dozens of depots shouldn't have them typed in one by one.

What we built

• Depots › Import in the portal: a CSV file, UTF-8, up to 500 depots. Columns: code, name, address, country, and optionally the old code a depot replaces.
• Dry run first, as for people: how many depots would be added and updated, and every problem.
• A depot is matched by its code, or by the old code in replaces, and updated; otherwise it is added.
• Nothing is ever deleted.
• Files that aren't UTF-8 are refused with a message saying so.

What we left out

• Moving people to their new depots. Use the people import afterwards.
• Deleting depots, and grouping depots into regions.

Rollout

Built for Vossberg and turned on for them first: Vossberg depot import notes. Other customers get it on request; support turns it on.