Subtle bug in Example for Dynamic Dimensions
In the example code for the Dynamic Dimension Service there appears to be a subtle bug which will affect refresh of the dimensions. ReadDynamicDimensionInfo(...) returns DateTime.Now: ' This api m...
Forum Discussion
I've not looked at the code, but tbh it shouldn't really matter - as long as you keep it consistent in all calls, you should get the expected behaviour.
So I would probably recommend using utcNow everywhere.
Passing DateTime.UTCNow time into DynamicDimensionInfo() or DynamicDataUnitData() does not render expected results when in an EST time-zone when I set the refresh/expiry time at 300 seconds, whereas DateTime.Now does work correctly. Presumably the app server must be converting the supplied time to UTC time, else there could be problems where users could be coming in from around the globe.