The material provided is for informational purposes only, and should not be relied on in making any purchasing or investment decision. The information is not a commitment, promise or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion. © 2026 Cloud Software Group, Inc. All rights reserved
Hi Andrew, I fail to see what benefit this will bring. A library item can have many properties, hence why they are stored on a child table. This is standard relational schema data modelling. Rather than asking for a feature, can you explain what are you trying to achieve and how this idea will help you do that? You can easily do a join with the LIB_PROPERTIES table and get all your keywords for each library item.