We have custom module with a record view that includes a number of CHECKBOXES which turn on or off saving to an external web service as well as saving to Sugar as usual.
These checkboxes are defined in the bean, and are used in the record view.
These checkboxes are NOT used in the dashablercord view.
When SAVING from the dashable record view (focus dashboard), the checkboxes are all updated to FALSE.
We can see in the developer toolbar NETWORK tab that the focus drawer does a full GET of the record via API (twice)
It also goes a GET of the record using "view=recordashlet" which is the fields for the focus dashboard panel.
When you EDIT in the dashboard, we have custom code to FETCH the record again (so we always edit from the most recent save), which again does an API GET of the recorddashlet fields.
When you then SAVE, it does an API PUT call, again with view=recorddashlet, but with ALL the fields from the bean.
Maybe it is using the DEFAULT values for the fields not in the view? It is the javascript on the client passing these, which the PHP on the server assumes is correct.
Has anyone else come accross the problem of fields being saved incorrectly from a dashlet?
Should we tweak the javascript code somewhere to NOT pass the fields wihich are NOT in the view?
Should we tweak the PHP API to NOT use the passed fields which are NOT in the view?