User Tools
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:adminmanual:businessmappings:masterdetailmapping [2021/04/27 01:40] joebordes [Generic Master Detail] |
en:adminmanual:businessmappings:masterdetailmapping [2021/06/06 16:26] (current) joebordes |
||
|---|---|---|---|
| Line 126: | Line 126: | ||
| <editable>0</editable> | <editable>0</editable> | ||
| <mandatory>0</mandatory> | <mandatory>0</mandatory> | ||
| + | <defaultvalue>0</defaultvalue> | ||
| + | <duplicatevalue>0</duplicatevalue> | ||
| <hidden>0</hidden> | <hidden>0</hidden> | ||
| <layout></layout> | <layout></layout> | ||
| Line 233: | Line 235: | ||
| This map can be used as infrastructure for you to create your own editor, but coreBOS will give you a generic editor if you create the map between two modules with a one-to-many (1:m) relation and create the necessary map and actions. | This map can be used as infrastructure for you to create your own editor, but coreBOS will give you a generic editor if you create the map between two modules with a one-to-many (1:m) relation and create the necessary map and actions. | ||
| - | For this to work, we have to follow some rules and set up an action. | + | For this to work, we have to follow some rules and set up two actions. |
| * In the business map record, the **target module** picklist field **MUST** be the detail module | * In the business map record, the **target module** picklist field **MUST** be the detail module | ||
| Line 243: | Line 245: | ||
| The link type is **DETAILVIEWWIDGET** and the module it is on has to be the Master module (Projects in the example above) | The link type is **DETAILVIEWWIDGET** and the module it is on has to be the Master module (Projects in the example above) | ||
| - | * List view datasource: the special value **corebos** means that the detail is a normal coreBOS module | + | * You must create a business action that loads the Master-Detail javascript code, something like this |
| - | * icon: in the header of the master-detail block we follow the LDS guidelines and prefix the title with an icon if given here. You can select any valid icon from LDS | + | |
| + | <code>include/js/masterdetailgrid.js</code> | ||
| + | The link type is **HEADERSCRIPT** and the module it is on has to be the Master module (Projects in the example above) | ||
| + | * List view datasource: the special value **corebos** means that the detail is a normal coreBOS module | ||
| + | * icon: in the header of the master-detail block we follow the LDS guidelines and prefix the title with an icon if given here. You can select any valid icon from LDS | ||
| + | [[en:adminmanual:businessmappings:CreatingGenericEditor|Read about the Making of the Generic Editor]] | ||
