Infor LN & Baan Tip of the Week: Limitations of Customer Defined Fields (CDFs)
Customer Defined fields are fields that can be added to tables, screens, reports, and BODs. Validation and calculation logic can be defined around those fields. This gives you great added capability and flexibility… however, are you aware of the limitations of using CDFs?
- You cannot define customer-defined fields for tables within Tools (the tl and tt 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 if editing the 4GL report layouts is still supported in your environment or by using the report personalization features of Infor LN Report Designer. 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. The actual number of fields in a table and the total length of all fields may be limited by the RDBMS you use.
- Only superusers 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.
If you have questions or need assistance with the use of CDFs, or Infor LN or Baan modifications in general, please contact us for assistance. We’d be happy to help. 800.762.2077 or kbarthelt@crossroadsrmc.com