Variant values in M-files and localisation errors in number calculations

Question

Dear all, 
 
 I have run into a problem that I hope you might be able to give some insight into. 
 
 I have a problem of where localised information in the M-files server was previously set to have the ',' (Comma) character as the decimal indicator but now it moved to '.' full stop. 
 
 This caused some calculations to add two zero's to each calculation where something was multiplied with a double. My problem now is with the DisplayValue property when retrieving the value from the server (vbscript) : 
 Ex. PropertyValues.SearchForProperty(1234).TypedValue.DisplayValue 
 
 In order to resolve this I am considering changing the DisplayValue to the Value function to ensure that the decimals would be understood in the current server context (independent from locale/regional settings). 
 
 My problem is when trying to cast the Variant dataType it does not relate to any known vbDataTypes. When I ask for the datatype is outputs datatype 8204: 
 VarType(PropertyValues.SearchForProperty(39).TypedValue.Value) 
 
 The above is for the state property which I understand should be text ( vbString (8): String) 
 
 Can anyone please help me to understand if it is possible to convert from Value : variant type to string / integer / double, or otherwise any good ideas to get past the , and . regional problem with double value calculations ? 
 
 Regards and thanking you for your help.

montua · Accepted Answer

Ok I realised my error. 
 
 When attempting to work with the Value property, use the TypedValue.DataType function to get the type of data. This will relate to one of the M-files datatypes ( https://developer.m-files.com/APIs/COM-API/Reference/#MFilesAPI~MFDataType.html) . 
 
 The Workflow state is from a list (lookup) so it should be managed as that type of object in the Variant type. 
 
 Use this function to get the Type if unsure and check the types in the property values in the admin tool. 
 oPropertyValue.TypedValue.DataType 
 
 (Also refer to the examples at the end of this page: https://developer.m-files.com/APIs/COM-API/Reference/#MFilesAPI~TypedValue.html ) 
 
 Long story short, when working with Real number data (numbers with decimals), best to not use the DisplayValue function and casting to double, rather use the TypedValue.Value function and then cast to the type (just make sure you know the type). 
 
 Thanks for your time ;)

Variant values in M-files and localisation errors in number calculations

Top Replies

Contact Us

Schedule a Demo

Careers

Trust Center

Privacy Policy

Security Hall of Fame

M-Files Community

Support Portal

Help Center

Product Center

Download M-Files

User Guides

Product News