Hi Ketan,
The date/time values you see in AML Studio and SQL Server are different for two reasons:
- The database stores date properties in the UTC representation of the corporate time zone, while clients display dates in local time. For example if I create a Part on a client in EDT, the client will show 2017-05-10T13:21:25. If the corporate time zone is not set or is also in EDT, the database will show 2017-05-10 17:21:25.xxx because 13:21:25 EDT = 17:21:25 UTC.
- The database stores a more precise time than is displayed in the client, hence the .xxx that appears at the end of a SQL datetime.
I don't believe it is possible to filter for an item's created date to the precision that is stored in the database (yyyy-mm-dd hh:mm:ss.xxx), but you can filter to the second an item was created:
<AML>
<Item type="Part" action="get">
<created_on condition="between">2017-05-10T13:21:25 and 2017-05-10T13:21:26</created_on>
</Item>
</AML>
If you know the precise date saved in the database, you can filter using a where clause in your AML:
<AML>
<Item type="Part" action="get" where="Part.created_on='2017-05-10 17:21:25.967'"/>
</AML>
Eli Donahue
Aras Labs Software Engineer
