I was hoping there might be a setting for the %DynamicArray and %DynamicObject classes to handle the numeric/string issues in that library globally, instead of property by property.
Otherwise I was just hoping hear what anyone else is doing, or maybe why they aren't concerned about the issue. Just to make sure the safe guards I mentioned are the best way before I start my upgrade.
One alternative may be to create a wrapper class with an identical interface to the %DynamicObject class so I could control setting properties. Of course inline initialization wouldn't work, but maybe using a macro and inserting a safety check would work -> $$$COS("[(someVal)]") to [($$SafeNumOrString^MyLib(someVal))]
Log in or create a new account to continue