Hi Isomorphic,
I have a problem with a DynamicForm with a ValuesManager and saving changed data here.
The same code did work with a end-November-build of 5.1p. It does no longer work with v10.1p_2017-03-02.
I'm not sure exactly what the reason is and could not isolate the root cause, yet. Are there any changes in the code in this area, that could help me narrow it down?
Calling valuesHaveChanged() in Developer Console prior to the save-attempt does return true.
In the result, I do not have a request in the RPC-tab and no error, warning, whatsoever in the Results-tab.
Do you have any idea what might happen here?
Setting client log-levels up turned to this finding - perhaps related, perhaps not, I don't know:
Blama
I have a problem with a DynamicForm with a ValuesManager and saving changed data here.
The same code did work with a end-November-build of 5.1p. It does no longer work with v10.1p_2017-03-02.
I'm not sure exactly what the reason is and could not isolate the root cause, yet. Are there any changes in the code in this area, that could help me narrow it down?
Calling valuesHaveChanged() in Developer Console prior to the save-attempt does return true.
In the result, I do not have a request in the RPC-tab and no error, warning, whatsoever in the Results-tab.
Do you have any idea what might happen here?
Setting client log-levels up turned to this finding - perhaps related, perhaps not, I don't know:
- See this sample (on the online showcase, on a newer version than my current 5.1p, it is on v11.0p_2017-03-06 as of now)
- Set all logging to 'Warn' and category 'RPCManager' to 'Debug'
- Change any Item, which results in this log entry
Code:15:29:39.961:MUP3:INFO:RPCManager:sendQueue called with no current queue, ignoring
Blama
Comment