The limitation of importing .gar files, is that they don't have a field for specifying the Client, however, there is a way to support having pre-created sites/locations across multiple clients and having them matched against what's in the .gar file.
First set up Short Codes to map the site names in the .gar file to what you want them to be in PATGuard Cloud.
- Go to the "More" menu
- Select "Short Codes"
- Select the "Site/Location" tab
- Select "Add" and set up mappings using Short Codes. E.g. LCC HOUSING OFF to Laois County Council Housing.
You will now need to set the Asset Mapping Strategy and import your .gar file.
- Set the option "Settings | Data | Asset mapping strategy = Site / Location / Asset Id mapping"
- Import your first gar file, and it will put everything into the selected Client (Unknown Client by default).
- Create Clients as needed, and move the Sites to the desired Clients.
- Now import another gar file.
- For every incoming location where there is at least *one* asset that can be found in the existing organiser tree with the same Site+Location+Asset Id, it will correctly place *all* assets from that incoming location into the expected organiser tree Client/Site/Location, i.e. yes, you can import a single gar file and have the results distributed across Clients as expected.
However, this doesn't work for locations in the incoming gar file where *none* of the asset ids match anything in the existing organiser tree - i.e. if your gar files have brand new asset ids each time, it will not be able to map them to the expected clients. At the moment there appears to no way to achieve this, but it does seem like a useful feature.