The same field appears with different labels or sizes on a screen (Custom or Primary) - Is this a data corruption with having 'duplicate' fields, is this an issue or why can this happen?

Version 1

    Details

    The same field appears with different labels or sizes on a screen (Custom or Primary) - Is this a data corruption with having 'duplicate' fields, is this an issue or why can this happen?




    Resolution

    [REASON]
    - The screen customizationfor primary or custom screens will always involve the following 2 tables:

    a. one where the actual
    field definition (Name, Type, Length, Description) + Read/Update rights + Log changes in history are defined. This information is stored in the CONTUDEF table and is part of the Contact Set tables

    b. one where most field properties like location, colors, label, screen size, required field etc are defined. This information is stored in the FIELDS5 table and is part of the GoldMine Base tables.

    - Any field from the CONTACT1 or CONTACT2 tables (defined in CONTUDEF table) can be put unlimited times on any screen and for each instance a new individual FIELDS5 table record will be generated with the identical VIEWID value
    >> Therefore for each instance a different label, different colors for label and / or data, different screen sizes etc can be determined for the appearance for this specific FIELDS5 entry although the underlying field always remains the same.



    place and adjust the USERDEF14 again on the Other screen


    there are now 2 FIELDS5 records with different field properties in the database (e.g. required, red label, data size extended)


    the field value is identical as the underlying field is USERDEF14

    The FIELDS5 shows 2 entries for the same VIEWID value



    - While GoldMine Technical Support does not recommend such a setup (as it usually does not make much sense to have the identical field two times on the identical screen) it is absolutely no contradiction and also no issue.


    - A more useful business case with the same technical background is often that the same field appears on different screens for example to have a field which should be straight away visible for all users (for example Account Manager) but should be also available on a certain screen where all 'Reps' for an account should be listed. In these cases the same underlying workflow applies but here the VIEWID value in the FIELDS5 would be different for the identical field.


    As in this case CONTACT1->KEY4 was used, the FIELDS5 table shows even more entries as the KEY4 field is also on other Primary views available in a demo database but every record has a different VIEWID




     
    Additional Information
    - This information is more detailed available in the related Knowledge Article #
    19231) and provides here only an generic overview

    1. When creating a new user defined field via Tools >> Configure >> Custom Fields >> New
    >> ONLY a CONTUDEF
    record (Field Definition - Name, Type, Length, Description) will be created,
    >> NO FIELDS5 record will be created as the user defined field will not yet appear on any screen
    >> Via the Rebuild a further column is created in the CONTACT2 table ONLY for the specific Contact Set the user defined field was created in

    2. When creating a new user defined field via Screen Designer / Place Field via either Right Click >> Screen Design >> New >> New Field or simply Right Click >> New Field >> New Field
    >> a CONTUDEF
    record (Field Definition - Name, Type, Length, Description) will be created, if Read/Update rights + Log changes in history will be set in the Field Properties dialog these will also stored in the CONTUDEF record
    >> a FIELDS5 record (
    most field properties like location, colors, label, screen size, required field etc.) will be created as the user defined field will now also be placed a screen
    >>  Via the Rebuild a further column is created in the CONTACT2 table ONLY  for the specific Contact Set the user defined field was created in


    3.
    When adding an existing field via Screen Designer / Place Field via either Right  Click >> Screen Design >> New >> Select the desired field from the Field drop down or simply  Right Click >> New Field >> Select the desired field from the Field drop down
    >> NO CONTUDEF
    record will be created as the user defined field (this can be also a primary field) already exists and is only selected
    >> a (further) FIELDS5 record (most field properties like location, colors, label, screen size, required field etc.) will be created as the user defined field will now also be placed a screen

    4. When changing the Field Properties from a field on a screen via Right Click >> Properties on a field on a screen
    >> NO CONTUDEF record will be created as the user defined field (this can be also a primary field) already exists and is only selected, if the Read/Update rights +  Log changes in history will be changed in the Field Properties dialog the CONTUDEF record will be changed as this information is stored in the CONTUDEF record
    >> NO (further) FIELDS5 record will be created but instead the related already existing FIELDS5 record will be changed

    5. When deleting a field from a screen via Right Click on the field on the screen >> Delete
    >> NO change to the existing CONTUDEF record as the field will be only be removed from the screen
    >> DELETION of the related FIELDS5 record (the field will be further available either on other screens or if on no screen anymore, it will be still available when creating Filters from the Contact Search Center column selection, from the Microsoft Word GMPlus integration field selection etc. 
     
    6. When deleting an user defined field via Tools >> Configure >> Custom Fields and Rebuild
    >> DELETION of the related CONTUDEF record of the current Contact Set
    >> DELETION of the related column in the CONTACT2 table in the current Contact Set
    >> NO change of the related FIELDS5 record >> This leads to a n/a display on the screen where the field resided previously as the underlying data from CONTACT2 is not available anymore