This is more of an issue with the User Guide AI rather than the Fibery system itself. I was working on creating an automation to update a User’s Department relations, and I was using Fibery’s User Guide. When asking the AI within the User Guide for assistance, one thing it said is “If [Step 1 Role].[Department] is a single entity, Fibery will treat it as a collection when used in this context.” This isn’t true (or at least it wasn’t in my case).
This did make me realize that I would love it if this behavior did exist. I find myself often wanting to work with single entities and collections.
I don’t know what you asked it about, but there are times when this is true, e.g. if you want to update a to-many relation field to Departments, it’s OK that your formula returns a single Department entity.
What would you love to be able to do? Is it somewhat connected to this?
No, my case is different. In this specific instance, I was trying to update the Departments to which a User is related. With our growing complexity, it looks like it is helpful for both Departments and Roles to be used as something like user groups.
So in this instance, I was attempting to create an automation where, when a User is assigned (people field) to a Role, then that Role’s related Department becomes related to the User (if it isn’t already). This isn’t straightforward since the User-Department relation is a collection while the Role-Department relation is singular.
I think all my instances of these kinds of needs center around either notifying or permissions.