In Progress

Incorrect exporting date via Document Templates. Case_creation_error via changing regional settings

Good day!

I want to point out a few facts incorrect application . And ask for help in solving problems.

1. Via Document Templates tool it was designed exporting table into Excel file. But it was found incorrect exporting the text fields. Namely, if the value of the field is " 2013-2", the value of cell is kind of "43598" in the file after the export (there is autoconverting values by ​​Excel ) .

I personally found a solution : via configuration wizard in the form mapping I added character "'" (single quote) to the value "2013-2". The resulting string is "'2013 -2"

How to correctly and efficiently solve it ?

2 . Via Document Templates tool it was designed exporting table into Excel file. But it was found incorrect exporting the date . For example, the value of the date is "09/01/2013" (1st September) . And after exporting:

- When cell in the template is formatted like "date" - the value of the cell is "09/01/2013" (there is autoconverting values by ​​Excel) . Moreover, conversion occurs when a date from 1 to 12 day of the month , and if the date above 12, for example, "17/09/2013" , the output value is normal -"17.09.2013 0:00:00", but the time is not necessary.

- When cell in the template is formatted like "text" - the value of the cell is "41283" (there is autoconverting values by ​​Exce) .

It was found a solution: to change the locale date format (from format like "mm/dd/yyyy" to

"dd/mm/yyyy") on the server for the system user (which generates an Excel file). Export works correctly concerning dates. But suddenly it was occurred 13 day of the month (or higher )(the

system date ), most of the processes can not be run , a window appears with the error: "

{"status":"error", "code": "CASE_CREATION_ERROR","type": "CaseCreationException", "message":

"The conversion of a varchar data type to a datetime data type resulted in an out-of-range value. The statement has been terminated. "}".

The investigation revealed the effect of the error was a new set the date format on the server. It was discrepancy of dates (my personal opinion: regional settings should not be so fatally affect the operation of applications). Changing the format of the dates on the server have been revoked (set "reset" for date format options). Processes can be run .

The residual error autoconverting values by ​​Excel was temporarily decided as follows: in the mapping form of a configuration wizard I added character "'" (single quote) to the date "09/01/2013". The resulting string is "'01.09.2013 0:00:00". And I cut time part "0:00:00" via substring function.

How to correctly and efficiently solve it ?

photo
0

Dear Illia,

A member of our support team will contact you by email

Regards.