| Auszug |
|---|
|
Nuclos dynamic business objects: data source, INTID, INTID_T_UD_GENERICOBJECT, dyn_ prefix, layout, status model, NuclosImage. |
Language: Deutsch · English
Dynamic business objects
Show data relationships as a read-only sub-form list – via a data source with INTID and INTID_T_UD_GENERICOBJECT.
| Status |
|---|
| colour | Blue |
|---|
| title | Application developer |
|---|
|
| Status |
|---|
| colour | Green |
|---|
| title | Updated: Jul 2026 |
|---|
|
| Status |
|---|
| colour | Grey |
|---|
| title | applies to Nuclos 4.2026.x |
|---|
|
What are dynamic business objects?
Dynamic business objects are used to view data relationships. Example: an order is assigned to a customer – on the customer you want to see the orders as a list. A dynamic BO produces that list.
Menu: Configuration → Data sources → Dynamic business objects
Creating via a data source
The data source requires two mandatory columns (unchangeable, must be part of the query):
- INTID – ID of the object storing the reference.
- INTID_T_UD_GENERICOBJECT – ID of the object where the data is embedded as a sub-form.
All further columns appear in the sub-form; the alias becomes the column header.
Data source of a dynamic business object.
Embedding in the layout
The dynamic BO is available in the layout like a normal BO; its name always starts with dyn_. Like normal BOs it must be added to the status model for permissions.
Dynamic BO in the layout.
| Info |
|---|
|
A dynamic BO is read-only – editing data is not possible. Use the context menu „show details“ to jump into the record. |
| Tipp |
|---|
|
For timestamps the alias must end in _as_timestamp (otherwise Nuclos truncates the time). Images (e.g. traffic lights) are not detected automatically – the metadata (t_md_dynamicentity.clbmetaxml or the .meta export) must be adjusted manually (<javatype>org.nuclos.common.NuclosImage</javatype>). |
Related pages
Charts
Similar principle.
Open →
