Issues with materialized views from HTS_ENUMERATION table in Biosar

Issues with materialized views from HTS_ENUMERATION table in Biosar

Customer created several materialized views from BIOASSAYHTS.HTS_ENUMERATION table so they could separate values from different Bioassay picklists. Those views will work as lookup tables in Biosar. Tables were exposed to Biosar from Bioassay and the lookup fields were defined in Manage Schema. Forms were created using REGDB.REG_NUMBERS as base table and Bioassay tables as child tables. Searching those forms works fine and the lookup fields show the correct values (strings from the materialized views) in the hitlists and the Search page. Problem: When the hitlist is exported to an SDF file the lookup values are lost for some of the fields while others work fine. Suggestion: Field length, spaces and special characters may have a negative impact on this feature. If a Bioassay field will be used to look up a value from a different table or view in Biosar, we recommend: - Bioassay field name lenght should not exceed 20 characters. - Bioassay field names should not include special characters, but letters and numbers only. - Bioassay field should not contain spaces.