Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Content Management (Extended ECM)
API, SDK, REST and Web Services
Attribute Oddities
Iva_Ilieva_(CTPAdmin_(Delete)_1417355)
Hi - I'm trying to set up a set of attributes that will allbe organized into a single category. I'm fairly new toLivelink and I'm finding a lot of idiosyncrasies.These consist of both undocumented limitations and behaviorthat is flat out not consistent with the documentation I dohave.Specifics:Docs say that you can't delete an attribute and create a new one with the same name. I can.Docs say that you can't remove an attribute from a categoryand then re-add it. I can.Un-documented issue: The name field is limited to 20 characters. Is this a hard limit or a configurable setting?Other things:I have encountered the 255 character limit on the totalsize of values for a popup field. Is there any work-aroundanyone's used to deal with this?I would also like to support multi-valued attributes. Thisdoesn't seem to be available. Is there a work-around? Myfirst thought has been to use a multi-line field for multi-line attributes and then separate the values by delimiter. After going down this road, I discovered another undocumented issue:You can only have one multi-line attribute per category in"Oracle" (the Livelink error I got specifically mentionedOracle, which is the DB we're using).Any thoughts on any of the above?Thanks in advance.
Find more posts tagged with
Comments
ray_chance
I don't know all the answers to all your questions, but I can tell you from experience that you don't want to delete an attribute or category, and then recreate it with the same name. If you load any documents using an attribute or category, then delete and recreate the attribute or category, you'll lose the information associated with the documents you put in. And the only way to correct it will be to delete the documents and then put them back in. When creating attributes and categories, you'll have to think about what you want very carefully and set your field lengths on the long side. A careful survey of your users is highly advisable. Once your attribute is created, your editing options are limited, and as the manuals say, you should not delete and recreate with the same name. The result is not pretty. (We use Oracle too, and I would expect you to see the same kinds of problems we did.) We have found that creating a variety of attribute categories offers the users a fair amount of flexibility, and they can set up different folders for different kinds of documents. Good luck with your attributes.
Lynne Drummond
Hi,We've experienced the same sort of problems with attributes. The biggy with us was the limit of 255 characters for use when defining a drop-down list.We're currently running SQL 6.5 in which the default type for the fields containing this information is VARCHAR(255).We raised this with support and asked if we could go ahead and change the type to TEXT (which supports massive blocks of text.) They gave us the go-ahead so we did this and it cured the problem. We were a bit uncomfortable with this as a solution, since tinkering with the schema is NOT something we want to have to do....If anyone knows of any plans by OT to change this, please let us know.CheersJonny
Ian_Lilleby__(ililleby_(Delete)_2058964)
There is now a product called LongPop (so called because it supports long lists in the pop-up fields). It enables your attributes to have an unlimited number of items, with a maximum of 1000 characters in the field.This addresses the most severe limitation of attributes for us, but beware - it is new, and we're still testing it.Regards,Phil BenjaminLivelink AdministratorEnron EuropeIf you want further info, email me on pbenjami@enron.com, not the email attached to this account.