Domain Validation process is unable to run successfully due to missing system fields on Domain table



For certain older customers on Domain Separation for whom the plugin may have been activated in a  preCalgary release, the normal ‘Domain Support - Domain Extensions Installer’ (com.glide.domain.msp_extensions.installer) plugin is not active on such instances and it is not recommended or advisable to activate this plugin after the fact for such customers. Typically for these customers only the com.glide.domain and com.glide.domain_basic plugins are active. 
When these customers upgrade to Istanbul and later releases, they are by design switched from the legacy Domain Numbering/Pooling method to Domain Paths by the upgrade process. 
However, since the instance does not have all the needed configurations (such as certain table fields etc.), this portion of the upgrade fails and they are not successfully switched to Domain Paths. As a result, essentially the Domain functionality on the instance is in a broken state. 
This knowledge article outlines some key changes that are needed on the customer instance prior to the upgrade, so that these issues are not encountered during upgrade.


Symptoms of Issue/Observed System Behavior: 

During upgrade and later, when validating Domain paths, the message: Default domain not set! Skipping orphan domain records’ appears. 
This is because the domain.default column is missing on such instances and needs to be created on the instance. 


In addition, Domain.Active and Domain.Primary fields may also be missing on such customer instances. 


Lastly, following 2 Business Rules would also be missing from their instance and would need to be imported from an out of box instance on the same release version as customer:

  • "Domain - Cache Default Domain Value"
  • "Domain - Validate Default"



    1. Hop on to the affected instance as a maint user with read/write access. (The steps below need to be done as maint)
    2. Go to System Definition > tables
    3. Filter the list where Table is domain and open the table record for the Domain table
    4. In the Column related list on the form, look for the 3 columns: Active, Default, and Primary
    5. Assuming you confirm these columns are missing on the instance, click the New UI Action on the Columns related list on the Domain table form to create these missing columns. Make sure to configure these columns exactly as per out of box settings.
    6. Go to Domain.list and set any one Domain record as the Default by setting the default field to True for that 1 record. Note: Only 1 domain record should have Default set to True
    7. Export the 2 business rules: "Domain - Cache Default Domain Value" and  "Domain - Validate Default"  from an out of box instance on the same release version as customer instance and with Domain Extensions Installer and other domain plugins active.
    8. Import these 2 business rules into customer instance
    9. Customer may proceed and delete the existing orphan records that the Domain Validation process has flagged, or set these orphan records to the Default domain, or the system should be able to handle setting them to the Default domain, once the Default field is added on customer instance and one of their existing domain records is set as the ‘Default’ domain
    10. Domain Validation should run successfully after following above steps and the domain paths should be set correctly by the Domain Validation process. 

Article Information

Last Updated:2018-01-16 00:55:52