The Enum type with base type Ref can prevent the automatic generation of virtual columns for [Related xx] in the referenced table.
Therefore, this technique is sometimes used when you want to display the keys of the referenced table in the form drop-down, but still keep good performance of the application.
When I used this recently, I noticed the following behavioral differences.
There are two tables shown below.
First shown is the behavior of the dashboard when desktop mode is off.
With the Enum type base type Ref, there is no interactive behavior in the view in the dashboard because there is no real relationship.
This is expected behavior.
Next, I turned on desktop mode and tried the same thing.
As you can see, when desktop mode is turned on, interactive behavior is achieved despite the lack of substantial relationships.
While this may seem gratifying at first glance, it seems to be a source of confusion in that the behavior in mobile and browser mode is different and inconsistent.
Is this intended behavior?
What do you all think? I would like to hear your opinions.
Solved! Go to Solution.
Unfortunately most of the differences between Ref and Enum-base-Ref are more historical accidents than design choices - places where something is checking specifically for "Ref" type columns in a way that overlooks Enum-base-Ref even though they should behave the same in most respects. I'm not sure what specifically changed here in Desktop, but generally we try to treat both kinds of Ref similarly and make the Enum behave more like the Ref when support issues involve these discrepancies, unless we know of a significant use case for the difference in behavior (e.g. suppressing the REF_ROWS column). In this case the inconsistency will probably be resolved in favor of the desktop behavior in some future mobile update.
User | Count |
---|---|
20 | |
13 | |
8 | |
3 | |
2 |