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 7 changed one line
|[Change Audit Logging|DETAILED CHANGE AUDITING|AUDIT LOGGING] is supported|Precise setup is needed, or the system may have problems
|[Change Audit Logging|AUDIT LOGGING] is supported|Precise setup is needed, or the system may have problems
At line 12 added 3 lines
%%warning
Note: UDC’s used in where clauses and find blocks, or as the 1st column of an LOV, can result in performance degradation. UDC’s are meant to contain supplemental information.
%%
At line 16 added 7 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 16 changed 6 lines
! A. In Personality
# Have all users sign out of system
# In IMCD form – add the new column with a [column usage|COLUMN_USAGE] of “User Defined Column”. Ensure that [Data Type|DATA_TYPE], [Domain Name|DOMAIN_NAME] and [Length|VALUE_LENGTH] are all entered at a minimum. Review other columns for samples, as needed.
# Exit from the Personality system
! B. In the Database
! A. In the Database
At line 29 changed one line
# Rebuild the workflow triggers:\\{{@SEED_CREATE_BIUD.sql\\@DB_RECOMPILE.sql\\}}
# Recompile the database:\\{{@DB_RECOMPILE.sql}}
# Rebuild the workflow triggers:\\{{@SEED_CREATE_BIUD.sql}}
At line 38 added 7 lines
! B. In Personality
# Have all users sign out of system
#Log in as MASTER
# In IMCD form – add the new column with a [column usage|COLUMN_USAGE] of “User Defined Column”. Ensure that [Data Type|DATA_TYPE], [Domain Name|DOMAIN] and [Length|VALUE_LENGTH] are all entered at a minimum. Review other columns for samples, as needed.
# Exit from the Personality system
At line 35 changed one line
# Sign in to the Personality system
# Sign in to the Personality system (Not as MASTER)
At line 37 removed 9 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 49 removed 2 lines
This page (revision-32) was last changed on 04-Jan-2023 15:27 by Kevin HiggsTop