CMDBuild Forum

Rest API card's date format

Old Versions
#1

Hello. 

With using of SOAP API I receive next date format: "dd/MM/yy HH:mm:ss", while with REST API I have another format: "yyyy-MM-dd'T'HH:mm:ss". Is it a bug? If so, are you going to fix it with next release?

Thank you for your attention. :)

#2
Dear Egor,
 
we are aware of this difference. The SOAP APIs have been designed a lot of time ago with the "mistake" of using "dd/MM/yy HH:mm:ss" as the date format. Later, for preserving compatibility, some new methods (like "getCardWithLongDateFormat" and "getCardListWithLongDateFormat") have been added. Those last methods use the same date format used within REST APIs ("yyyy-MM-dd'T'HH:mm:ss").
 
So, we are sorry but it's a mistake that unfortunatly we should maintain for backward compatibility at least for some other time, but surely it won't change for the next release.
 
Best regards.
 
-- CMDBuild Team
 
Previously Egor wrote:

Hello. 

With using of SOAP API I receive next date format: "dd/MM/yy HH:mm:ss", while with REST API I have another format: "yyyy-MM-dd'T'HH:mm:ss". Is it a bug? If so, are you going to fix it with next release?

Thank you for your attention. :)

 

#3
Ok. I see. Thank you for the response. But I couldn't find any of the methods in Webservices.wsdl even in the last release of cmdb. 
 
Previously Tecnoteca wrote:
Dear Egor,
 
we are aware of this difference. The SOAP APIs have been designed a lot of time ago with the "mistake" of using "dd/MM/yy HH:mm:ss" as the date format. Later, for preserving compatibility, some new methods (like "getCardWithLongDateFormat" and "getCardListWithLongDateFormat") have been added. Those last methods use the same date format used within REST APIs ("yyyy-MM-dd'T'HH:mm:ss").
 
So, we are sorry but it's a mistake that unfortunatly we should maintain for backward compatibility at least for some other time, but surely it won't change for the next release.
 
Best regards.
 
-- CMDBuild Team
 
Previously Egor wrote:

Hello. 

With using of SOAP API I receive next date format: "dd/MM/yy HH:mm:ss", while with REST API I have another format: "yyyy-MM-dd'T'HH:mm:ss". Is it a bug? If so, are you going to fix it with next release?

Thank you for your attention. :)