[CLOSED] getRecordsValues now uses Mapping instead of Name

[wazige]

Hi. Since upgrading from ExtNet 1.0 revision 3141 to the current version there seems to have been some changes in how getRecordsValues () on the Store works.

Given we have a recordfield definition like this:

<ext:RecordField Name="example" Mapping="Example" />

when calling getRecordsValues() in the older version it used to be serialized using the Name property as:

{example: "value"}

However, with the latest version it seems to use the Mapping property, so:

{Example: "value"}

Is this intentional? Because if so it would mean a lot of rewriting of our current solution.

[Vladimir]

Hi,

Yes, it was changed intentionaly.
You can prevent it by adding custom config to the store

Name="saveMappings" Value="false" Mode="Raw"

or pass config object to getRecordsValues method

store.getRecordsValues({mappings:false})

[wazige]

Ok, thanks for the heads up!