Attribute Fields Limitation

Hi Experts,

Just few basic questions.

I want to know that how many static values can be enterted for a particular custom attribute of a custom object type. Is there any limitation?

I have around 4000 attibute field values to be added from composer project as part of creating an object type with custom attributes.

Is it possible to add 4000 attribute field?

Does it seems to be feasible?

Any performance or object creation issue with such a long list?

What if I need to add another 1000 or more attribute fields? Is that again possible?

Is there any limitation for these attributes fields value numbers or character size?

What is the alternate approach to add these many attribute field values if it is not possible them to add as static fileds value using composer?

Kindly let me know.

Thanks in Advance

Find more posts tagged with

Comments

msroth

Without knowing all the details, my gut reaction is that 4000 attributes on a custom object type is WAY too much. I would suggest trying to model your content differently and reducing your metadata set to 20-30. Perhaps the other data can be put in some relational tables outside of the DCTM table space and referenced with the r_object_id as a foreign key.

DCTM_Guru

I'm pretty sure you will encounter DQL string length error when you initially try execute CREATE type with 4000 attributes. You might be able to get around this by creating type without any attributes and execute ALTER TYPE as batch scripts.

Keep in mind even if can create a type with these many attributes, any time you perform an object fetch, your DFC client will try to download and cache all of the object's attribute values.

kcvipin

Hi,

Thanks for your answers. I think you misunderstood my question.

I am not talking about adding 4000 attributes to a custom object type. What I am asking here is a custom attribute with 4000 fields which should appear as a drop down values for the custom attribute.

I already have the custom attribute created along with 6 drop down fields. Now I have to add another 4000 fields and there are chances that we could be adding more fields in future.

(For Example, Month is my attribute name and January, Feburary ....are the 12 fields values for this attribute, like wise I have to add 4000 fields for my custom attribute and show them in drop down)

There drop down fields are currently added as comma separated values in the composer as static fields when created the object type.

I am going to use them into DCO client and unfortunately DCO does not support the value assistance and hence I can not use these fields as registered table column also.

What my concern was, If I try to add these 4000 fields for the custom attribute, Does Composer allow to add such a long charcter sequence which may be at the length of 10000 characters for these 4000 fields.

Additionally, is it feasible to add so many fields for a custom attribute.

There fields are currently available in an excel spread sheet. Is there any DQL/API/DFC script/code available which can insert these fields for the custom attribute and avoid the manual process overhead.

I hope, I am clear now.

Please let me know your inputs on this.

DCTM_Guru

Gotcha.

"What my concern was, If I try to add these 4000 fields for the custom attribute, Does Composer allow to add such a long charcter sequence which may be at the length of 10000 characters for these 4000 fields."

- As I indicated before, you might encounter a char limit in the length of the DQL that gets executed behind the scenes.

"Additionally, is it feasible to add so many fields for a custom attribute."

- Not sure about Composer limitation, but I havent ever encounter any limitation on value assistance query against a table. Keep in mind, the more values you have the longer it will take to render jsp/html page. Not sure if individual browsers have limitations on number of fields in a dropdown list.

"There fields are currently available in an excel spread sheet. Is there any DQL/API/DFC script/code available which can insert these fields for the custom attribute and avoid the manual process overhead."

- If convert xsl to csv, you should be able to write a simple DFC program to read the file and write to the object.

kcvipin

Hi Johnny,

Thanks for the quick response.

I will try to add some will check if there is any char limit from documentum or composer side.

Unfortunately, I have to use these values as drop down in DCO client and DCO does not support the query based value assistance and hence can not use a registered table also. I have to add them as Fixed values only in the composer.

DO you have any DFC program which can read these fields from csv file and add them to the attribute as attribute fixed values?

One more thing I want to know, I already have the object type and attribute created and some documents also got created for this custom object type with the existing values of the custom attribute. Just wanted to confirm that, updating these additional fixed values to attribute should not be a problem even if the object instances exist.

Thanks

msroth

Ah, got it. I don't know about limitations in the software to handle a list that size, but I would still be concerned about users having to pick a single value from among 4000+ possibilities. You might want to rethink your informaiton architecture a little bit and see if you can break these values into sub-groups or use some AJAX to ease data entry.

Vipin

Hi Johnny and Roth,

Can you please help me in providing a DFC code which cab add these fields values to the attribute?

Thanks

DCTM_Guru

Look in the DQL manual, under ALTER TYPE. There should be an example of how to add VA values.