# Using date and times with Xano **URL:** \ **Category:** External Collections, Custom Actions & Collections\ **Created:** [January 27, 2021, 7:48pm UTC](https://forum.adalo.com/t/using-date-and-times-with-xano/8444 "2021-01-27T19:48:52Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![rickman](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/rickman/32/555_2.png) [@rickman](https://forum.adalo.com/u/rickman)\ **Post date:** [January 27, 2021, 7:48pm UTC](https://forum.adalo.com/t/using-date-and-times-with-xano/8444/1 "2021-01-27T19:48:52Z")
Anyone using Xano for external collections. I’m having an issue getting the date/time coming from Xano to be in the right format for Adalo components. I change the Unix to Y-m-d H:i:s but Adalo reads them as text rather than date. ---
**Author:** ![JL\_LJ](https://avatars.discourse-cdn.com/v4/letter/j/f08c70/32.png) [@JL\_LJ](https://forum.adalo.com/u/JL_LJ)\ **Post date:** [January 30, 2021, 5:42pm UTC](https://forum.adalo.com/t/using-date-and-times-with-xano/8444/2 "2021-01-30T17:42:19Z")
Hi, I haven’t used xano yet, setting it up to move away from Airtable. But have you tried to check the format in the external collection? You can change the field format: ![image](https://us1.discourse-cdn.com/flex020/uploads/adalo/original/2X/1/1d5eb398e1faf3a2adb3ed8f5b1ffa9aa72074c6.png) Btw can you share how you filter data from Xano? in the lists? Thank you very much. ---
**Author:** ![rickman](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/rickman/32/555_2.png) [@rickman](https://forum.adalo.com/u/rickman)\ **Post date:** [January 30, 2021, 8:35pm UTC](https://forum.adalo.com/t/using-date-and-times-with-xano/8444/3 "2021-01-30T20:35:31Z")
![Screen Shot 2021-01-30 at 2.33.48 PM](https://us1.discourse-cdn.com/flex020/uploads/adalo/original/2X/9/9db05c0efea945e1d84a87e1ab6fe64fa2a19661.png) Here is a screenshot of my xano API call to GET a list of appointments. My trouble is now POSTing a new appointment with 2 timestamps in a format Xano can read correctly. ---
**Author:** ![rickman](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/rickman/32/555_2.png) [@rickman](https://forum.adalo.com/u/rickman)\ **Post date:** [January 30, 2021, 8:37pm UTC](https://forum.adalo.com/t/using-date-and-times-with-xano/8444/4 "2021-01-30T20:37:37Z")
Also, here is a link to a video showing how to GET timestamps formatted correctly. [![](https://us1.discourse-cdn.com/flex020/uploads/adalo/original/3X/8/4/8461e327a5449303a78c98bc5170f17b44ca6960.jpeg "Adalo and Xano - Using Xano Timestamps in Adalo Screens") ](https://www.youtube.com/watch?v=JAaEoPnn8Ho) ---
**Author:** ![pablob8](https://avatars.discourse-cdn.com/v4/letter/p/c37758/32.png) [@pablob8](https://forum.adalo.com/u/pablob8)\ **Post date:** [November 16, 2022, 4:27pm UTC](https://forum.adalo.com/t/using-date-and-times-with-xano/8444/5 "2022-11-16T16:27:49Z")
Interestingly, Adalo somehow recognizes the _created\_at_ field that comes as a default with any of my Xano external collections. I looked at the settings to see if this timestamp was set up differently, but looks just like the others. Adalo doesn’t even have it as a timestamp field type, and the Magic Text input also relabeled the field “create\_at” to “Date Created” … odd. TLDR: Adalo probably has some “date created conversion” function to read _created\_at_ timestamps from Xano external collections. My suggestion is to ignore this rabbit hole and stick to doing the time format function described here for all timestamps in Xano APIs ---
**Author:** ![JL\_LJ](https://avatars.discourse-cdn.com/v4/letter/j/f08c70/32.png) [@JL\_LJ](https://forum.adalo.com/u/JL_LJ)\ **Post date:** [November 16, 2022, 5:49pm UTC](https://forum.adalo.com/t/using-date-and-times-with-xano/8444/6 "2022-11-16T17:49:01Z")
Xano uses the Epoch Unix Timestamp, the reason that Adalo recognizes, is that most databases use that timestamp as metadata (created, modified dates), so it is common, you can check here conversions. > **[Unix Time Stamp - Epoch Converter](https://www.unixtimestamp.com/)** > > Epoch and unix timestamp converter for developers. Date and time function syntax reference for various programming languages. Keep in mind that when you send a date to Xano from Adalo, you do need to a conversion in the unix timestamp to miliseconds, as some use format in seconds, others in miliseconds. ---
**Author:** ![pablob8](https://avatars.discourse-cdn.com/v4/letter/p/c37758/32.png) [@pablob8](https://forum.adalo.com/u/pablob8)\ **Post date:** [November 16, 2022, 7:25pm UTC](https://forum.adalo.com/t/using-date-and-times-with-xano/8444/7 "2022-11-16T19:25:03Z")
@JL_LJ My post did a poor job of describing the issue: - I have created a _modified\_at_ timestamp field for each table in my Xano instance. - It looks to have the same settings as the _created\_at_ field that is pre-built with every table - When I’m doing an external database, everything tells me these two fields are sent exactly the same way to adalo. BUT… Only my _created\_at_ is being recognized as a timestamp. The _updated\_at_ timestamp (along with any others) is being treated as a standard number entries. Can’t change the field type in the database dropdown menu in Adalo’s side, can’t change the way the number is displayed on the screen editor. This is constant and repeatable across more than one table, which led me to believe that Adalo does not actually recognize Epoch Unit Timestamp, but has instead created a function that searches for that _created\_at_ field and transforms it (and only that one) internally before allowing the Adalo user to manipulate that field. Can anyone replicate this issue or is this a problem with my setup?