| Customer defined fields (OP)You
can use the Customer Defined Fields (CDF) sessions in LN to store additional
information in tables without creating so-called customizations. These sessions
are available in the Tools menu, under Application Configuration. Configuration To configure customer defined fields: - Start the Customer Defined Fields Parameters (ttadv4590m000) session. Select CDF Active and click OK.
- Define customer defined fields in one of these ways:
- Use the Customer Defined Fields option in the View menu of an already started
session.
Use the Customer Defined Fields (ttadv4591m000) session. If you want to create customer defined fields of type
‘List’, specify the lists and their constants in the Lists (ttadv4592m000) and List Constants (ttadv4593m000) sessions.
Start the Convert to Runtime Data Dictionary (ttadv5215m000) session. Convert the customer defined
fields and the related domains to the runtime data dictionary.
Note If you use the DEM Content Pack with Infor LN, consider
using the MIT0200 (Customer Defined Fields) wizard to set up Customer Defined Fields. You can execute this predefined wizard from
the Wizards by Project Model (tgwzr4502m000) session after you specified the business function model for your company. Limitations - You cannot define customer defined fields for tables within the
tl and tt Tools packages.
- External integrations, such as Infor Integration,
EDI, Office Integration, and SOA-based integration, do not support customer
defined fields.
- You can use customer defined fields within 4GL reports, as far
as editing the 4GL report layouts is still supported in your environment. For
external reporting, only Infor Reporting and Microsoft Reporting (SSRS) support
customer defined fields.
- Customer defined fields cannot store application data in
multiple data languages.
- There is no direct limitation on the number of CDFs in a table.
However, the actual number of fields in a table and the total length of all
fields may be limited by the RDBMS you use.
- Only super users can run the Convert to Runtime Data Dictionary (ttadv5215m000) session to convert the customer
defined fields and the related domains to the runtime data
dictionary.
Note The full functionality of customer defined fields is only
available within Web UI and LN UI.
Customer defined fields are not displayed in the classic Infor LN BW UI. Personalization A session can contain two types of customer defined
fields: - Customer defined fields of the main table. These are regular
customer defined fields. If set to active, these fields are initially visible
in the session. See Customer Defined Fields (ttadv4591m000).
- Referenced customer defined fields. These are active customer
defined fields that belong to a table that is referenced by the main table of
the session. Referenced customer defined fields are initially invisible in the
session.
A referenced customer defined field is linked to a session if
its table is referenced through: - A table definition (so-called hard-reference)
- A reference specified in the form definition, in particular in
the Input/Ref Express property of a form
field
- A
query.extend.select() call in the UI script of the session
If a session contains customer defined fields, you can perform
these actions: - Hide/unhide these fields.
- Move these fields to a different location, such as a different
tab.
See Personalization Workbench (ttstppers ). Related documentation For more information about customer defined fields, see
"Customer Defined Fields" in the Infor LN Extensions Development
Guide. | |