0041476: API Change: Columns that use the Date reference will only store date part (and not time part) in the database

Description

The current behaviour of columns that use the Date reference is the following:
- When saving a record from the ERP, the incoming date value has the YYYY-MM-DD format, and the data is stored with 00:00:00 as the time part.
- When the value is programatically set (i.e. order.setOrderDate(new Date()) ), then both the date and the time part of the given date will be stored in the database.

The proposed change is to automatically strip the time part for values used in columns that use the Date reference.

Impact: Only those flows that were programatically setting dates with a time part, and then retrieving the store date and using the time part would be affected.

Those affected should use the DateTime reference instead.

Steps To Reproduce

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

related to

design defect

0040905

new

AugustoMauch

It would be fine to automatically truncate the value if the reference is date

Notes
(0114063) AugustoMauch (administrator) 2019-08-19 09:45	The issue this API change was related with has been moved to design defect, will not be done in the near future

Issue History
Date Modified	Username	Field	Change
2019-07-29 17:03	AugustoMauch	New Issue
2019-07-29 17:03	AugustoMauch	Assigned To	=> alostale
2019-07-29 17:03	AugustoMauch	OBNetwork customer	=> No
2019-07-29 17:03	AugustoMauch	Modules	=> Core
2019-07-29 17:03	AugustoMauch	Triggers an Emergency Pack	=> No
2019-07-29 17:03	AugustoMauch	Relationship added	related to 0040905
2019-07-29 17:05	AugustoMauch	Description Updated	View Revisions
2019-08-19 09:45	AugustoMauch	Note Added: 0114063
2019-08-19 09:45	AugustoMauch	Status	new => closed
2019-08-19 09:45	AugustoMauch	Resolution	open => invalid