Hello,
I am currently exporting configuration from one UAT environment and importing the entity data into another environment. I am doing the export/import with data file type EXCEL.
I am experiencing issues on import and have deducted that the issue is related to any column that contains decimal, e.g. rounding precision. To clarify here is an example, when I export the Sales Tax Codes entity from the UAT environment I get an excel file containing the data and in one column (rounding precision) I get the value ,00000. When trying to import this file into the other environment I get the following error message "The file for entity Sales Tax Codes has 7 error(s), '0' Sales Tax Codes record(s) inserted in staging" (7 in this case being all the sales tax codes that have been set up in the UAT environment).
I tried creating the sales tax codes immediately in the new environment and exported the entity to see if there were any differences in the source files. Turns out the decimal in the column "rounding precision" has vale .00000 rather than ,00000. This despite the setup being the same. If I take the original file from UAT export and replace comma (,) with point (.) I get a successful import, and this goes for other entities.
As this is not a sustainable long term solution I am wondering if anyone has some input as to how we might export the files in a correct format (containing point as decimal). We have tried changing system language, user language, time/date format. No matter what combinations we use, or what is displayed, the problem is the same. Any exports from UAT comes out with decimals as comma, while the exports from the new environment comes out as points (which seems to be what is required for the import as well).
Thanks in advance,
Kindly,
O
