Dataverse to Fabric OneLake - Part 9 - DateTime and Currency Values

Querying Dataverse DateTime and Currency values initially seemed like it would be too easy to bother creating a video for, but as I started looking at the nuances of how these values are stored in Dataverse and how they appear when we query them through Fabric, I realized this is an interesting topic! -
DateTime values are stored in Dataverse, not in the user's timezone, but rather in GMT/UTC timezone - so what the user sees onscreen could be quite different from what is stored in the database. - For reporting, I like to shift the datetime to a timezone that works for the customer and ensure all dates are standardized to that timezone. - If you're an organization that deals with lots of timezones already - this is something you're already familiar with.
For Currency fields - if you only ever have a single currency in your database - your reporting job is simple - but if you have multiple currencies in your records, you'll likely want to ensure that any currency values that are ever aggregated are standardized to the same currency. - (i.e. you'd never add up a column containing values in multiple currencies.) - The _base values are the fields in Dataverse that are stored in a single currency set by the environment as the base currency.)
#dataverse #dynamics365 #dynamics365crm #fabricators #microsoftfabric #powerbi #fabric