Make CSV Tulip user import possible (and improve export?)

Product Suggestions
, , , ,
1

Greetings.

I’ve recently been working with a table containing users. I wanted to fill this table with a test dataset to evaluate some app behavior under more realistic conditions. However, I noticed that for columns of type User:

  • Exporting to CSV simply adds the user’s full name in the CSV (which is ambiguous if two users share the same name),
  • and importing users via CSV seems to be impossible.

I think it would be good if:

  • An exported user CSV value also contained the Tulip user ID to guarantee unicity.
  • A user could be imported using the Tulip user ID.

Both of these needs could be fulfilled if, for example, the user was represented as a CSV value with a format such as <full-name> (<tulip-user-id>), e.g.: John Doe (xip7DXdLOJDgo4Iio).

What do you think?