This page (revision-32) was last changed on 04-Jan-2023 15:27 by Kevin Higgs

This page was created on 26-Nov-2021 10:22 by rforbes

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
32 04-Jan-2023 15:27 3 KB Kevin Higgs to previous
31 03-Jan-2023 14:04 3 KB Kevin Higgs to previous | to last
30 15-Jun-2022 11:25 3 KB Kevin Higgs to previous | to last
29 26-Nov-2021 10:22 3 KB Kevin Higgs to previous | to last USER DEFINED COLUMN ==> USER DEFINED COLUMN (UDC)
28 26-Nov-2021 10:22 3 KB khiggs to previous | to last
27 26-Nov-2021 10:22 3 KB khiggs to previous | to last
26 26-Nov-2021 10:22 3 KB rforbes to previous | to last
25 26-Nov-2021 10:22 3 KB khiggs to previous | to last
24 26-Nov-2021 10:22 3 KB khiggs to previous | to last
23 26-Nov-2021 10:22 3 KB rforbes to previous | to last
22 26-Nov-2021 10:22 3 KB rforbes to previous | to last
21 26-Nov-2021 10:22 3 KB rforbes to previous | to last

Page References

Incoming links Outgoing links
USER DEFINED COLUMN (UDC)
USER DEFINED COLUMN (UDC)

Version management

Difference between version and

At line 15 added 8 lines
!BEST PRACTICES for User Defined Columns
* Create the Column on IMCD with a number range in excess of 9000
* Identify the column in the database with a name prefix that is unique to your organization (.e.g BEN_DUE_DATE rather than just DUE_DATE)
* User Defined Columns are recommended over User Defined Fields if you are going to use them for __any__ processing (where clauses, workflow, approvals, loading, etc.). If you are just storing data to be reported on, user defined fields may be sufficient to the task.
* Lexicons that are associated to a User Defined Column must be prefixed with "X_" (.e.g X_CUST_VALUE rather than CUST_VALUE)
* The name of the User Defined Column should not start with a number. Depending on its planned usage in the application, this will cause errors that are not apparent with initial or form setup and usage (usercalcs).
At line 41 removed 6 lines
!BEST PRACTICES for User Defined Columns
* Create the Column on IMCD with a number range in excess of 9000
* Identify the column in the database with a name prefix that is unique to your organization (.e.g BEN_DUE_DATE rather than just DUE_DATE)
* User Defined Columns are recommended over User Defined Fields if you are going to use them for __any__ processing (where clauses, workflow, approvals, loading, etc.). If you are just storing data to be reported on, user defined fields may be sufficient to the task.
* Lexicons that are associated to a User Defined Column must be prefixed with "X_" (.e.g X_CUST_VALUE rather than CUST_VALUE)
* The name of the User Defined Column should not start with a number. Depending on its planned usage in the application, this will cause errors that are not apparent with initial or form setup and usage (usercalcs).
At line 48 removed one line
This page (revision-32) was last changed on 04-Jan-2023 15:27 by Kevin HiggsTop