Currently, we need to use SetLoadFields to define, if fields will be excluded from a FindSet/Get. This leads to extending necessity the Base App or other base solutions to prevent performance issues.
When creating a TableExt, setting a default value for each field would give us the possibility to still use TableExt, but not compromise existing processes. For my own processes, I will use SetLoadFields. Other processes that don't need my field, will not need to implement SetLoadFields in best case.
TableExt
{
fields
{
field(....) {
DefaultJoinBehaviour = Loaded or Unloaded
}
}
Comments
That's a cool idea. You could extend this by a table property, in connection with a function LoadTableExtension(MyExtension). this way you wouldn't have to mark all fields individually or the SetLoadFields(...) would be shorter when you load all fields.
Category: Development