This page (revision-9) was last changed on 26-Nov-2021 10:22 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
9 26-Nov-2021 10:22 1 KB Kevin Higgs to previous USER DEFINED COLUMN ==> USER DEFINED COLUMN (UDC)
8 26-Nov-2021 10:22 1 KB ihowie to previous | to last
7 26-Nov-2021 10:22 1 KB ihowie to previous | to last
6 26-Nov-2021 10:22 1 KB rforbes to previous | to last
5 26-Nov-2021 10:22 1 KB rforbes to previous | to last |
4 26-Nov-2021 10:22 1 KB rforbes to previous | to last
3 26-Nov-2021 10:22 1 KB rforbes to previous | to last
2 26-Nov-2021 10:22 1 KB rforbes to previous | to last
1 26-Nov-2021 10:22 1 KB rforbes to last

Page References

Incoming links Outgoing links
USER DEFINED FIELD
USER DEFINED FIELD

Version management

Difference between version and

At line 2 added 5 lines
*End users can create these and no special knowledge of the system is required
*Date sensitive changes will carry forward the values
*UserCalcs can read these values, but Workflow UserCalcs cannot access the NewValue of them
*Can be accessed using the [P2K_SMGETUDF] function by external report writers and by [P2K_SMPUTUDF] by stored procedures to set the value.
*Interface programs like [UEEF] and [UPPHF] can access these natively
At line 3 changed 9 lines
||Pro||Con
|End users can create these and no special knowledge of the system is required|The data is stored in an abstraction table and is not natively linked to the table it is related to.
|[Date Sensitive|DATE SENSITIVE] changes will carry forward the values|This abstraction has the potential, if there are a lot of user defined fields, to impact performance
|UserCalcs can read (not update) these values|Any use of a user defined field in any kind of processing (programming, where clauses, lists of values) is not recommended. Instead, please consider the use of a [user defined column|USER DEFINED COLUMN|USER DEFINED COLUMN (UDC)]
|Workflow UserCalcs cannot access the NewValue of them|No change audit logging is available for UDFs
|Supported by [Object Security|IMOS] and [Form Object Security|IMFOS]|
|Interface programs like [UEEF] and [UPPHF] can access these natively, within the tables identified|
|Can be accessed using the [P2K_SMGETUDF] function by external report writers and by [P2K_SMPUTUDF] by stored procedures to set the value.|
|Does not require database access or system restart|
!Points opposed to User Defined Fields
* The data is stored in an abstraction table and is not natively linked to the table it is related to.
* This abstraction has the potential, if there are a lot of user defined fields, to impact performance.
At line 13 changed 2 lines
!!Setup and Use of a User Defined FIELD
Use the [IMUF] screen to define the User Defined Field on the table you want the data related to. Note that in a parent-child table relationship where there are date-sensitive children, the parent table is often not permitted to have user defined fields (as seen on [IMTD])
!!Setup and Use of a User Defined Field
Use the [IMUF] screen to define the User Defined Field on the table you want the data related to. Note that in a parent-child table relationship where there are date-sensitive children, the parent table is often not permitted to have user defined fields (as seen on [IMCD])
At line 16 changed 6 lines
----
![Notes|Edit:Internal.USER DEFINED FIELD]
[{InsertPage page='Internal.USER DEFINED FIELD' default='Click to create a new notes page'}]
You may also want to decide on [User Defined Columns|USER DEFINED COLUMN] as your extension structure instead.
This page (revision-9) was last changed on 26-Nov-2021 10:22 by Kevin HiggsTop