_1 is undefined at ISC_DataBinding.js:1725

[levi]

Hi,

I'm getting a JS Exception _1 is undefined at ISC_DataBinding.js:1725

It's maybe an odd case:
While trying to figure out another JS Exception (elem is null in some place I can't seem to find), I tried unbinding my ListGrid from its ValuesManager and let the VM data operation run on its own.
So this ValuesManager does not have any DBC members.


The initial fetch on the VM works fine,
then I do an update operation, which gives me this exception.
The request & response look fine and have status SUCCESS.
I do not get the exception when I again bind my grid to the VM.

XRP6:WARN:Log:TypeError: _1 is undefined
    unnamed() @ target/sc/modules/ISC_DataBinding.js:1725
    ValuesManager._saveDataReply({Obj}, {Obj}, {Obj}) @ target/sc/modules/ISC_Forms.js:3124
    anonymous({Obj}, {Obj}, {Obj}) @ target/sc/modules/ISC_Core.js:60
    [c]Class.fireCallback(_1=>"isc_targetValuesManager_3.$49z(dsRequest,..."[ 59],  _2=>"dsResponse,data,dsRequest",  _3=>[object Array],  _4=>{Obj},  _5=>undef) @ target/sc/modules/ISC_Core.js:323
    [c]Class.fireCallback(_1=>"isc_targetValuesManager_3.$49z(dsRequest,..."[ 59],  _2=>"dsResponse,data,dsRequest",  _3=>[object Array]) @ target/sc/modules/ISC_Core.js:421
    DataSource.fireResponseCallbacks({Obj}, {Obj}, {Obj}, {Obj}) @ target/sc/modules/ISC_DataBinding.js:584
    DataSource._completeResponseProcessing({Obj}, {Obj}, {Obj}, {Obj}, {Obj}) @ target/sc/modules/ISC_DataBinding.js:581
    DataSource._handleSCServerReply({Obj}, {Obj}, {Obj}) @ target/sc/modules/ISC_DataBinding.js:1886
    [c]Class.fireCallback(_1=>{Obj},  _2=>"rpcResponse,data,rpcRequest",  _3=>[object Array],  _4=>{Obj},  _5=>undef) @ target/sc/modules/ISC_Core.js:323
    [c]Class.fireCallback(_1=>{Obj},  _2=>"rpcResponse,data,rpcRequest",  _3=>[object Array]) @ target/sc/modules/ISC_Core.js:421
    anonymous(callback=>{Obj},  request=>{Obj},  response=>{Obj},  data=>{Obj}) @ target/sc/modules/ISC_DataBinding.js:1327
    unnamed({Obj}, {Obj}, {Obj}, {Obj}) @ :186
    [c]RPCManager.fireReplyCallbacks(_1=>{Obj},  _2=>{Obj}) @ target/sc/modules/ISC_DataBinding.js:1332
    [c]RPCManager.performOperationReply(_1=>{Obj},  _2=>{Obj}) @ target/sc/modules/ISC_DataBinding.js:1326
    RPCManager._performTransactionReply(138) @ target/sc/modules/ISC_DataBinding.js:1319
    [c]RPCManager.performTransactionReply(_1=>138,  _2=>"//isc_RPCResponseStart-->[{data:{costCe..."[ 25040],  _3=>undef) @ target/sc/modules/ISC_DataBinding.js:1279
    anonymous(138, [object XMLHttpRequest]) @ target/sc/modules/ISC_Core.js:60
    [c]Class.fireCallback(_1=>"isc.RPCManager.performTransactionReply(..."[ 67],  _2=>"transactionNum,results,wd",  _3=>[object Array]) @ target/sc/modules/ISC_Core.js:323
    [c]Comm.performXmlTransactionReply(_1=>138,  _2=>[object XMLHttpRequest]) @ target/sc/modules/ISC_Core.js:1305
    anonymous([object XMLHttpRequest]) @ target/sc/modules/ISC_Core.js:60
    [c]Class.fireCallback(_1=>"isc.Comm.performXmlTransactionReply(138..."[ 58],  _2=>"xmlHttpRequest",  _3=>[object Array],  _4=>[object Proxy],  _5=>true) @ target/sc/modules/ISC_Core.js:323
    Comm._fireXMLCallback([object XMLHttpRequest], "isc.Comm.performXmlTransactionReply(138..."[ 58]) @ target/sc/modules/ISC_Core.js:1278
    unnamed([object Event]) @ target/sc/modules/ISC_Core.js:1290
    unnamed() @

Does this say anything?
thanks,

SC_SNAPSHOT-2012-01-19_v8.3d/Pro Deployment (built 2012-01-19)

[Isomorphic]

The usage of a ValuesManager with no members is essentially unsupported and quite likely to lead to odd errors. It's something that would never be done in a real application (if you wanted to manipulate data in a DataSource without any visual components, you'd call databinding APIs on the DataSource directly).

If you think this error can occur while the VM has errors, or you have a requirement for this use-case in your application that we hadn't anticipated, please let us know and we'll take a look

Thanks
Isomorphic Software

[levi]

Thanks, understood. Was low prio and bad usage, as I thought.

For some flows, we could just 'get and do something' because of a user's interaction with some widget (rather than the user directly manipulating the data via a DBC).
Since we use VMs all over the place for datasource handling, it would be easy to follow the same code pattern and use one there as well.

I'll have to keep in mind to use the DataSource directly.