Thought I’d share this little use-case, mostly so maybe new people can see the things you can do with Fibery.
This isn’t a tutorial—I’m just going to glance over it to give you a rough idea of how it works, but can go into depth if anyone wants.
Goal
- Every time we create a new folder with a customer’s name in our NAS, we want it to appear as a new entity in Fibery.
- We also want the folder to be associated with a customer (an entity) in Fibery, which can be achieved through the relations.
- We don’t want to spend time manually assigning Folder → Customer relationship.
Setup
On our end
On our NAS server we create a folder for each customer named by their ID, underscore, and then short format of date (as they can be recurring): 1234_031120, 1235_031120, and so on. The customers ID is automatically created by our accounting platform, which is a webapp.
Through the power of their API, Fibery’s API, and a NodeJS program, we’ve also fully automated importing the customers from accounting in to Fibery.
In Fibery
Each folder means a serie of things we need to do, so I made the folder its own entity and added the State extension for progress (sorry, it’s in Norwegian):
The name of the entities are the names of the folders. Next I created a formula field for folder entities that uses Regex to get the customer ID part. Finally, I created a one-to-many relationship from folder to customers, and with the power of the auto-linking relationship I could have it target my formula field to the Customer ID field of customers.
I took the Regex in the formula from the announcement. Very convenient indeed 
The result
All entities and relations are fully automated. Blue entities are folders, and the linked purple are the customers.
Entities show up max 5 minutes after creation. By adding a some caching/storing on our end, I also don’t make any unnecessary API requests.
I also made it so the network paths are included inside each entity, so you only have to copy-paste to go in to the folder.
