this problem is a migration from smartclient 8.2
Version SC_SNAPSHOT-2012-02-16_v8.2p/PowerEdition
to
SmartClient Version: v10.0p_2015-02-02/Pro Development Only (built 2015-02-02)
google chrome Versión 43.0.2357.130 m
i expose the problem:
creating a listgrid with this definition :
will generate a wrong gui presentation and also will have problems generating a filter. In version 8.2 it goes smoothly because it only uses the name of the field as a javascript object with its associated value but in version 10 it makes interaction when first parts of datapaths are named as the name of a field. and also generates a horrible named filter js object
We've been able to transform the filter in the defaultfilter to the one with the names(manualgenerated) and not the datapaths as in previous version and saved the filter (autogenerated) and in the callback using listgrid.filterEditor.setValuesAsCriteria(,,,) set back the listgrid to the autogenerated in order to keep the values in the listgrid filter editor record.
But this is a workaround that doesn't make me too happy so, would it be possible to know exactly how to proceed in this case? or if impossible could a property be added to tell smartclient to generate this filter automatically with the old-style name convention instead of the where datapath exists use datapath and when not use name? this doesnt happen only in listgrid but in select items etc
Version SC_SNAPSHOT-2012-02-16_v8.2p/PowerEdition
to
SmartClient Version: v10.0p_2015-02-02/Pro Development Only (built 2015-02-02)
google chrome Versión 43.0.2357.130 m
i expose the problem:
creating a listgrid with this definition :
Code:
Fields: [
{name: "codigo", width: 100, canSort: true, dataPath: "conceptoNomina/codigo", align: "center"},
{name: "descripcion", width: 400, canSort: true, dataPath: "conceptoNomina/descripcion"},
{name: "empresa", width: 100, title: isc.Mpxi18nProperties.company, canSort: false, dataPath: "empresa/codigo", align:"center"},
{name: "codDelegacion", width: 100, title: isc.Mpxi18nProperties.delegation, canSort: false, dataPath: "delegacion/codigoProvincia", align: "center"},
{name: "producto", width: 100, title: isc.Mpxi18nProperties.product, canSort: false, dataPath: "producto/codigoEstructura", align: "center"},
{name: "lineaVenta", width: 100, title: isc.Mpxi18nProperties.saleLine, canSort: false, dataPath: "lineaVenta/codigoEstructura", align: "center"},
{name: "convenio", width: 100, title: isc.Mpxi18nProperties.agreement, canSort: false, dataPath: "convenio/codCompuestoConvenio", align: "center"},
{name: "cliente", width: 100, title: isc.Mpxi18nProperties.customer, canSort: false, dataPath: "cliente/codigoCliente", align: "center"},
{name: "subproyecto", width: 100, title: isc.Mpxi18nProperties.subproject, canSort: false, dataPath: "subproyecto/codCompuestoSubproyecto"},
]We've been able to transform the filter in the defaultfilter to the one with the names(manualgenerated) and not the datapaths as in previous version and saved the filter (autogenerated) and in the callback using listgrid.filterEditor.setValuesAsCriteria(,,,) set back the listgrid to the autogenerated in order to keep the values in the listgrid filter editor record.
But this is a workaround that doesn't make me too happy so, would it be possible to know exactly how to proceed in this case? or if impossible could a property be added to tell smartclient to generate this filter automatically with the old-style name convention instead of the where datapath exists use datapath and when not use name? this doesnt happen only in listgrid but in select items etc