Importing data to a Team
Considerations when importing to a Team
For a bulk import file, destination Teams cannot be specified. To import into multiple Teams, an export file for each Team is required. Then, import directly to an existing Team by initiating the import tool from within the destination Team. Other Team import approaches are provided below.
Caution
Existing Collections belonging to Teams can be imported by conditioning an import file with Bravura Safe column headers, which include Collections. However, similar to items, importing Collections this way ALWAYS creates the specified Collection(s), even if a Collection with the same name already exists. This can cause duplicate Collections.
Other approaches for importing to Teams and Collections:
Import items to a 'personal' safe first, then move items to Teams and Collections using multi-select and move actions.
See:
Import items into an existing Team, and then manually assign items one-by-one to Collections.
Note
Items within a Team cannot be multi-selected for actions.
Import items into a single Team with a conditioned CSV or JSON file that specifies Collections and create the Team's Collections during import.
Devise a script leveraging the Bravura Safe API to take an import file as a source file.