You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
current problem that date is expected to be dd.mm.yyyy. dd.mm.yy has to be manually corrected before continuing the process
diffing on file level is possible, but once saved as CSV from Excel, next to the data format, also the number format is contorted, e.g. 0.0 is saved as 0, depending on the number format, the digits after the decimal point may even be rounded, what not only obfuscates the diff but may even change the content.
Cons:
diffing on file level will not be possible
Steps:
have the prepare task create an XLSX instead of CSV
have the export task expect an XSLX istead of CSV
If it is cheap to support both CSV and XLSX (with XLSX as default), prefer that.
The text was updated successfully, but these errors were encountered:
This will resolve a few open issues:
Pros:
dd.mm.yyyy
.dd.mm.yy
has to be manually corrected before continuing the processdiff
ing on file level is possible, but once saved as CSV from Excel, next to the data format, also the number format is contorted, e.g. 0.0 is saved as 0, depending on the number format, the digits after the decimal point may even be rounded, what not only obfuscates the diff but may even change the content.Cons:
diff
ing on file level will not be possibleSteps:
prepare
task create an XLSX instead of CSVIf it is cheap to support both CSV and XLSX (with XLSX as default), prefer that.
The text was updated successfully, but these errors were encountered: