Views:

Overview

When you are upgrading from a version prior to 1.0.0.460  you may need to perform additional steps over the standard solution import. 

CreateRecord() & UpdateRecord()

The setting of dates has changed in release 1.0.0.460 for the CreateRecord() and UpdateRecord() functions. In previous versions these functions used to set a datetime field with the local timezone. This has now been changed so that it now uses UTC timezone.

This makes several things easier to do like,

  • Reduces the need to use UtcTimeFromLocalTime() or LocalTimeFromUtcTime() functions.
  • Improves consistency, in using  UTC datetimes

Steps to take,

  • Review all formulas using either the CreateRecord() or UpdateRecord() functions where a date field is being set.
  • If using UtcTimeFromLocalTime() or LocalTimeFromUtcTime() in most cases you can just remove.
  • For other formulas determine if this change from a local datetime to UTC datetime would affect the business logic

Note 1 : 

As always perform testing to ensure this change does not affect your business requirements in an adverse manner.

Note 2 : 

Handling and Setting Dates
https://support.north52.com/knowledgebase/articles/489359-handling-and-setting-dates

Note 3 : 

If you have any formulas using the LocalTimeFromUtcTime() function please test to ensure the desired outcome.

If you run into any difficulties please contact support@north52.com for further assistance. 

 

Did you know?

You can easily copy/clone test data in TestShield

Once you have set up test data with TestShield it is easy to create a copy/clone and make changes. It is centrally stored so that all users creating tests can use the test data in their tests. This approach dramatically reduces the time it takes to create tests, enabling teams to deliver Dynamics 365 projects faster and at less cost.

Learn more about TestShield