10-08-2016, 08:31 AM
column_fields: Great, thanks.
related_tables: Ah, so bassically you could add some tables that do not follow the skeleton-protoype and use columns from it later on?
list_fields and list_fields_name: Wow, powerful that business mapping can override these. Very useful. But, suppose I wouldn't use Business mapping, am I using these arrays correctly here? Fot instance, can I use this relation to indicate that the lookup should be in accounts table? What will be automatically done here? Or should I use only my own module's tables?
Ah, that makes sense, using them only as a starting point.
Thanks for your help so far again!
related_tables: Ah, so bassically you could add some tables that do not follow the skeleton-protoype and use columns from it later on?
list_fields and list_fields_name: Wow, powerful that business mapping can override these. Very useful. But, suppose I wouldn't use Business mapping, am I using these arrays correctly here? Fot instance, can I use this relation to indicate that the lookup should be in accounts table? What will be automatically done here? Or should I use only my own module's tables?
Ah, that makes sense, using them only as a starting point.
Thanks for your help so far again!