Automations Find Records: what are the field type limitations? Error says: "No valid nested options"
Hi all,
I am curious to learn more about what linked and un-linked data can be used in the 'Find Records' action in Automations.
This happens frequently, and I am fairly sure that it is related to field data types. Linked record fields can only be used in certain instances, and lookup fields can only be used in others. Sometimes I have had to create 'String' fields through formulae to lookup other records.
My ask: does anyone have any links to learning resources or documentation where i can learn what the limitations/benefits of certain field types are. We are managing the database through a front-end, and no fields are updated manually, so the vagaries of these data types and their capacity/limitations is quite a challenge!
An example of my issue is included in the screenshots attached:
For reference, I am working with 5 tables:
Users
- In some cases linked to Organisations
- In some cases linked to Properties
Properties
- Linked to Users
- In some cases linked to Leases
Units
- Linked to Properties
Leases
- Linked to Organisations
- Linked to Properties
Tasks
- In some cases linked to Properties
- In some cases linked to Units
- In some cases linked to Organisations
- In some cases linked to Users
