Different combo values in each cell

Suite and Optimus Suite 7
#1

I know that I can create “coro” column type with combo-values. But this will be applicable for the whole column. I would like to specify the combo values per cell. Is that possible?

Example:
1st row possible values: A, B, C
2nd row possible values: A, B, C, D, E, F
3rd row possible values: C, D
…

#2

In the case of the dhx.Suite 7 usage it is not supported (as you’ve created a post in the dhtmlxSuite 7 topic).
But, as you are talking about the “coro” column type, and it is available in the dhtmlxSuite 5 only, you are able to use the getCustopmCombo() method to generate a combo collection for a specific cell:
https://docs.dhtmlx.com/grid__managing_selectbox_collection.html

1 Like
#3

Hello @ddmb

I guess I did that in this example, check it and tell me if was of any help:

The old example:
https://snippet.dhtmlx.com/8lc41zwo

The new example:
https://snippet.dhtmlx.com/shqmvjrh

1 Like
#4

There is a typo in your snippet: for the second row you’ve defined the “complexity: 1”, but I suppose You’ve meant “complexity: 2”

#5

Hello @sematik

No, I just keep 1 in the second row. You can change the value in the column complexity to change the options in the column scale.

But I improved the example:

https://snippet.dhtmlx.com/shqmvjrh

I guess this example is more clear. We also check that the column salary is not outdated when complexity change.

We still having a limitation, I guess we can’t use the DataProxy to load options dynamically when the user filter, so we can’t handle extremely big collections yet. I hope we can do that in the future, even in the GPL version :pray::smile:

Greetings :vulcan_salute:

1 Like
#6

I see. Thank you for your clarification and a pleasant example.

We still having a limitation, I guess we can’t use the DataProxy to load options dynamically when the user filter, so we can’t handle extremely big collections yet. I hope we can do that in the future, even in the GPL version !

Thank you for your suggestion. I’ve sent it to the dev team, and it will observed. I’ll inform you about any news on this issue.

1 Like
#7

This doesnt work that smooth when u have a real world example.
What i mean is that you have (ID, VALUE) pairs with the same value for each key.

but if u have a pair like this:

id: “SOME STRING OR NUMBER”,
value: “SOME DIFFERENT STRING”

When u change the column options on the fly everywhere in the grid column the values will be replaced with their IDs.

So if originally u have a column like this:

column name

France
Italy
Germany
USA

after changing the options u will have:

column name

12
8
3
90

where 12, 8, 3 and 90 represent the the ID of the id,value pair

#8

Hi @Nikolai_Dimentiev, you are right :sweat:

I guess I solved this issue in this example:
https://snippet.dhtmlx.com/txefc1cg

Of course, this is not the ideal solution. But I guess it works.
Let me know your opinion.

Greetings :vulcan_salute:

#9

Hello.

We’ve extended the possibility to define an individual options collection for the combo/select/multiselect cell in the dhx.Grid in our latest update (v8.1.0).
You can check it in the following snippet:

Please, download the latest available dhx.Suite build from your client’s area to get this and other new features.
More details about this update can be found here:

Thank you for your report.