Setting the DateEffective property could cause audit details to be inaccurate on some business layer objects

Setting the DateEffective property could cause audit details to be inaccurate or Account History records to be created uneccessarily on the following business layer objects:

• finAccountCreditLimitChange
• finAccountDefaultInterestChange
• finAccountInterestCycleChange
• finAccountInterestRateChange
• finAccountMinimumPaymentChange
• finAccountMonitorCategoryChange
• finAccountOtherInterestChange

These objects have been updated so that setting the DateEffective property will refetch any of the 'Original' and other read-only properties on the object. This means that checking the 'HasChanges' property on these objects should always yield the correct result.