Export a filtered list

You have a Site schema holding clinics. Let’s get some of them out as a CSV, edit it in a spreadsheet, and push the changes back in.

Export what you are looking at

Open the Site list (Asset Management > Sites) and search for the clinics you want - say country:FR. Then choose Action > Export.

The Exporter opens with your search query already filled in and the current view’s columns already ticked. That is the shortcut: whatever you had narrowed down on the list page is what you are about to export.

You can also reach the tool empty from the sidebar (Tools > Exporter) and pick a schema there.

Pick your columns

The panel on the right lists every column the schema can export, with a checkbox each. Tick what you want; the order shown is the order you get in the file.

Two boxes are ticked and greyed out: _schema and keyname. They are what makes the file re-importable, so you cannot drop them.

Use Select all to take everything, then untick the few columns you do not need - usually faster than ticking a dozen. The button becomes Select none once everything is ticked.

Columns tagged injected resolve a reference for you - on a clinic that points at a hosting site, hosting__city gives you the site’s city. They start unticked, and they are export-only: being computed, they are not written back on import.

Get a CSV you can re-import

Choose Format: CSV, then in Options set Add an _action field to noop, and press Export. The file downloads immediately.

Open it in a spreadsheet. It looks like this:

_action,_schema,keyname,displayname,country,city,...
noop,site,ANCON,Ancon Surgical Day Clinic,FR,Lyon,...
noop,site,BELAIR,Belair Medical Centre,FR,Nantes,...

The first two columns make this round-trip safely:

• _action is noop on every row, so re-importing the file as-is changes nothing. It comes first on purpose: it is the column you are about to edit.
• _schema tells Cavaliba which schema each row belongs to.

Now edit a cell - fix a phone number, say - and change that row’s _action from noop to update. Leave every other row at noop. Save as CSV.

Push it back

Go to Tools > Import, pick your file, press Check to confirm it parses, then Import. Only the rows you set to update are written.

This is the safest way to do a bulk edit in Cavaliba: export with _action: noop, change the rows you mean to change, re-import. Nothing you did not touch can move.

Large exports

If your search matches more than a few thousand objects, the export does not download straight away: it runs in the background and a window shows you progress, counts and an estimated time left. A download link appears in that window when it finishes, and the file stays available for a day.

You can press Abort to stop it. If you have the task permissions, Hide closes the window and leaves the export running - follow it from the Tasks menu in the top bar.

What’s next

• Try Format: YAML with Inline refs set to site on the Certificate schema: each certificate comes out with its clinic’s own record attached under _refs.
• Tick an enumerate column and export as YAML: its subfields come out too, right after it. They are not offered as checkboxes because they depend on the value each object selected - and for the same reason they never appear in a CSV.