Date field output in SUP HWC application using OData service

[former_member196814]

Hi All,

I am currently working on a SUP HWC MBO based application using OData service. We are using SUP 2.1.3 with Odata service and created a MBO in SUP for the getting the details via Odata service on Gateway.

overview:

The Get_details Service i am using has one Date field which shows the Orignal Date when a particular approval/rejection request is created in the ECC system. When i execute this OData service on browser it gives me the correct Date of request creation as well as the output result in MBO is also correct and matches with the Backend entry.

Issue:

Date field data on Browser and MBO is same and correct but the date coming on the device is always showing the current day's date instead of the orignal date of request creation.

since i have validated that the data received till MBO is correct but getting manipulated when seen on the device(iOS & Android)

I would request yo all to share your experience and help on this issue.

Regards

Rahul

[former_member196814 · Accepted solution]

Changing the field size accordingly solved this issue.

Thanks you all.

[Jitendra_Kansal]

Good to hear you have resolved your issue. Please close this thread by marking solution as correct answer.

Regards,

JK

SCN Moderator

[former_member196814]

Hi All,

I am receiving the above log for date field error in SCC

[former_member196814]

2014-12-05 07:02:12.600  Subsystem=Error  Application ID=HWC, Application Connection ID=c9d1aac1-be3d-3041-a9d1-5e6e25b6e7e6__HWC, User=xyz@mwfSecurityConfig, Correlation ID=, Package=hbl_cm_mwfv1:1.0, MBO=hbl_payrq_detail, Operation=findByParameter, Thread ID=1776, Node ID=server300, Error=231#HBLCMMWFv1:1 suppowf d1_hbl_cm_mwfv1.1_0 (MessageChannel Thread-1776) com.sybase.vader.cache.CacheUtil::truncateStringAsNeeded:321 - EIS character column crval too long. The EIS column length is 10.  Maximum column length in cache is 8.  Converting to null.