Field design problem for approval level + assigned user entity reference

Michael Chen

6/5/24, 8:02 AM

Say I have an approval system that needs to assign to users by levels with a limit of 5 levels

(say choose limit as 2 levels, then level 1 => uid 3, level 2 => uid4, that makes it a two level approval node).

Which setup of backend field is better on a decoupled system?

Create a single entity reference field, use the delta weight as level for the user being referenced within.
Create two field (integer list field + entity reference field), use integer list field as level and entity reference field for user.
A combined field to depict both integer list and entity reference field by each row (similar to paragraphs, but without layers of revisions control).

I feel like the second approach will be more straight forward and clean to handle with while the first approach is a twist of smart backend coding. But that may be a technical debt in the future?

Which is a better approach and why?

0 + 0

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Field design problem for approval level + assigned user entity reference

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.