Best practice for field type

What is the best way to add a field to a type?
As a type/object or as a unique id? How does it effect the performance?

(I have a type called Record. It has a field called customer. Should field customer be of type User or of type Text, and contain the uniqe id of the User?)


Hey @chagit.hazani

It depends on the use case of course but for that specific example you should definitely create the Customer field of type User. Then you can reference the User in workflows.

If you go with a text field, it makes it a lot more complicated. It would mean you would have to manually reference the unique_id for each Record and do searches to retrieve the User for that unique_id

Thanks a lot!