[atomatom]

great. good to know.

the javadoc could be improved here for these non-string cases (or multiple value string cases) , and perhaps made clearer with some examples. i would imagine the use of optionDataSource id->string is probably more common than an optionDataSource with just a string.

Description copied from interface: DataBoundComponent
Retrieves data that matches the provided criteria and displays the matching data in this component.

This method behaves exactly like fetchData() except that textMatchStyle is automatically set to "substring" so that String-valued fields are matched by case-insensitive substring comparison.

question: my workaround of doing the id->string and then string-id conversion on the server seems like it should not be necessary (i have not reverted my workaround since using filterdata instead of fetchdata) - i read you reply above as saying it was the correct way of doing this - this seems wrong to me; shouldn't the client code should handle id -> string mapping (and string -> id)

[Isomorphic]

Docs and samples such as SQL -> Large Value Map show a join in which both the id and display value delivered to the client. No server-side translation of values should be necessary unless you are having to do joins manually for some reason.

[Tilds]

I'm having the same issue as the original post about the group by problem when multiple options are selected.

SmartClient Version: v8.2p_2012-09-17/Pro Deployment (built 2012-09-17)

Firefox 16.0.1

RPC Response:

{
    "operationId":"estimate/functionPoint/functionPoint_fetch", 
    "transactionNum":8, 
    "httpResponseCode":200, 
    "transport":"xmlHttpRequest", 
    "status":0, 
    "httpHeaders":{
        "Content-Type":"text/plain; charset=utf-8", 
        "Cache-Control":"no-cache", 
        "Expires":"Thu, 25 Oct 2012 13:23:12 GMT", 
        "Pragma":"no-cache", 
        "Transfer-Encoding":"chunked", 
        "Server":"Jetty(6.1.x)"
    }, 
    "isStructured":true, 
    "results":{
        "data":[
            {
                "functionPointId":3, 
                "count":1, 
                "description":"test", 
                "complexity":"AVG", 
                "functionPoint":4, 
                "hours":96, 
                "tag":[
                    15, 
                    16
                ], 
                "type":"EI", 
                "cost":9600
            }, 
            {
                "functionPointId":5, 
                "count":1, 
                "description":"test 2", 
                "complexity":"LOW", 
                "functionPoint":4, 
                "hours":96, 
                "tag":[
                    16
                ], 
                "type":"EO", 
                "cost":9600
            }
        ], 
        "invalidateCache":false, 
        "isDSResponse":true, 
        "operationType":"fetch", 
        "queueStatus":0, 
        "status":0
    }, 
    "isDSResponse":true, 
    "invalidateCache":false, 
    "data":[
        {
            "functionPointId":3, 
            "count":1, 
            "description":"test", 
            "complexity":"AVG", 
            "functionPoint":4, 
            "hours":96, 
            "tag":[
                15, 
                16
            ], 
            "type":"EI", 
            "cost":9600
        }, 
        {
            "functionPointId":5, 
            "count":1, 
            "description":"test 2", 
            "complexity":"LOW", 
            "functionPoint":4, 
            "hours":96, 
            "tag":[
                16
            ], 
            "type":"EO", 
            "cost":9600
        }
    ], 
    "startRow":0, 
    "endRow":2, 
    "totalRows":2
}

I'm grouping by the tag column, I have attached a screenshot of how the listgrid looks when the group by is applied

In your answer to atomatom you said to check if the live value was still an array. Im not sure how to do that.

/Tilds

[Tilds]

Bump

Im still having problems with this. Anyone have an idea whats wrong?