nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Doctype creation- Value mapping referring to an external table.

Prashaanth

I have created a doctype where the conditional value mapping for an attribute gets the query results from a table in another DB registered in documentum.

This registered table contains about 1.6M users from the LDAP. The deployment of this docapp took much longer than usual , but was successful.

I am now trying to create documents and the performance is really slow. I am kind of sure its because of the MV thats being referenced.

Apart from indexing the table I cannot think about anything else to improve the performance. Kindly post me on suggestions to improve performance, or if there is any other solution to address accessing an table from a remote DB.

Find more posts tagged with

Comments

DCTM_Guru

I dont think value mapping was designed for that many rows. I would customize the component class and query for the value directly using DQL and populate the control.

Prashaanth

To provide more info on this problem, I am using a DQL query here as value assistance.

The query is run on the registered table in docuementum to populate values on the Webtop interface.

Also, please let me know if writing a TBO would improve performance.

DCTM_Guru

Please provide more information on your use case. Is the user entering a name in text box and then you are using value assistance query to return something? Is it only returning single value or multiple values?

TBO is only triggered when you save the object. It is NOT triggered during changes in the UI. This is where customizing the component class comes into play.

Prashaanth

The attribute is a repeating attribute and the results are populated soon after the user proceeds clicking on next button on the file->new->Document. The query populates the values on the UI and the text entered by the user filters the values accordingly by the default documentum feature which searches by the 'Begins with' search pattern.

This is the query I use in the value mapping "select name from dm_dbo.LDAP_users"

DCTM_Guru

The issue is that you have a dropdownlist that potentially has 1.6M values. Is this correct? If so, of course this it takes forever to load - I'm surprised that the application doesnt hang.

The efficient way to do this is to use Ajax to search for username based on what user types in textbox.

Prashaanth

Thats not a drop down, a repeating attribute where you click an edit button and a new page pops up with all the results on the left box and the right box where you add users. The default documentum feature. Fortunately the application works. I should certainly customize the component class. Also try including ajax to improve search. Thanks a lot for all the inputs.

DCTM_Guru

Picklist and dropdown loads same way; it just displays it differently. The performance issue has to do with how many values you are populating in the control. Its similar to trying to open a folder and display 1.6M files underneath it.

Prashaanth

Since I am adding the query to display all 1.6M users as a value map in composer, all values are populated in the control. And I think that the set of results fetched by the query will be displayed in the control ,which would let us choose desired value(s) from it.

DCTM_Guru

I guess what I am trying to say is that your performance issue is to be expected. You can write simple HTML page that contains 1.6M values and see how long it takes to load.

Prashaanth

Thanks again for all the inputs.