[CLOSED] [1.0] GridPanel CheckColumn

[methode]

Hi all,

I use a Store bound to an XpoDataSource. I have a CheckColumn inside the GridPanel, at inserting and editing the Grid, if I leave the checkbox unchecked - false - I got an error, bad response. My DLL is up to date, 1.0.

<ext:Store ID="Store1" DataSourceID="XpoDataSource" runat="server" OnAfterRecordUpdated="Store_AfterRecordUpdated"
        OnRefreshData="Store_RefreshData" RefreshAfterSaving="Always" OnAfterRecordInserted="Store_AfterRecordInserted">
        <Reader>
            <ext:JsonReader IDProperty="Oid">
                <Fields>
                    <ext:RecordField Name="Oid" />
                    <ext:RecordField Name="Name" />
                    <ext:RecordField Name="Active" Type="Boolean" />
                </Fields>
            </ext:JsonReader>
        </Reader>
    </ext:Store>

GridPanel Columns
...
<ext:CheckColumn ColumnID="clmActive"  Fixed="true" Editable="true" Width="70" Header="Active" DataIndex="Active">
                                </ext:CheckColumn>

Is that a bug? Usually my code worked fine with CheckColumn in grid.

Thanx

Matteo

[Vladimir]

Hi,

Can you create an example which reproduces the error? If you have bad response then it is server side problem. Can you post response (from FireBug, for example)?

[methode]

Hi Vlad,

please, see the images in attachment, hope it helps.

About FireBug, what tab should I inspect to better investigate the problem?

Moreover, in the code, I used to do a .Save() inside AfterRecordInserted event to concretely save the object to the database, now it is not needed, it saves anyway, if I do save code inserts two lines in db.

Thanx

Matteo

[Vladimir]

Hi,

I think you havet to set default value for Attivo RecordField

<ext:RecordField Name="Attivo " Type="Boolean" DefaultValue="false" />

[methode]

Hi Vlad,

yes confirm, it solved it.

Should people always set that property? Maybe it would be more convenient having it set by default to true/false,
than the developer can chose what value to write according to his need.

Thanx

Matteo

[Vladimir]

Hi,

I don't think that it should always has default value because in some cases it is need to have undefined default value and know whether a user choose some value or not (for example, developer can use combo for editing boolean field with none, false or true values)