Change in behaviour for ValuesManager.getValues()?

[stonebranch2]

Hi Isomorphic,

Can you confirm if there has been a change in behaviour with the method ValuesManager.getValues() between "SmartClient Version: v10.1p_2016-06-09/Pro Deployment (built 2016-06-09)" and "SmartClient Version: v10.1p_2016-08-11/Pro Deployment (built 2016-08-11)?

In cases where the method previously returned an empty map, we are now seeing default values.

Regards

[Isomorphic]

This may be related to your other thread where you've noticed that setValuesManager() now causes the form to go through initialization? Calling getValues() on a ValuesManager that has initialized would be expected to have default values returned.

[stonebranch2]

That being said, relating to the other thread, was there a behavioural change with respect to the setValuesManager() initialization logic? Was this intentional? If you intend to reply to the other thread with the specifics, I will await feedback on that thread.
Thanks

[Isomorphic]

Yes, setValuesManager() was broken and was fixed. Please wait for details on the original thread.