Time fields, when present in dataset header and/or detail, assume the date specified for ActivityDate. If ActivityDate changes, existing values are not updated accordingly and the Time field then adopts the new ActivityDate. When in the detail or if multiple time fields exist in header, this behavior results in different dates appended to Time fields for the same activity (see image). This behavior is also different than the importer tool which appends a date = '1901-01-01' to all fields w/ data type = Time. I recommend all fields w/ data type = Time behave in the same manner as the importer so time data is stored consistently regardless of how the data is brought into the system.
Time fields, when present in dataset header and/or detail, assume the date specified for ActivityDate. If ActivityDate changes, existing values are not updated accordingly and the Time field then adopts the new ActivityDate. When in the detail or if multiple time fields exist in header, this behavior results in different dates appended to Time fields for the same activity (see image). This behavior is also different than the importer tool which appends a date = '1901-01-01' to all fields w/ data type = Time. I recommend all fields w/ data type = Time behave in the same manner as the importer so time data is stored consistently regardless of how the data is brought into the system.