QlikView 12.10:
Running a reload including a WHERE clause in which the field is a date (format mm/dd/yyyy) changes the numeric representation to #####.
Running a reload including a WHERE clause in which the field is a float value changes the value to a numeric value and drops the decimals when the number is an integer. e.g. 10.00 turns into 10
QlikView 12.50:
The reload maintains the original data type/formatting from the source.
Environment
Resolution
This was an intended change in behavior.
Workaround:
It will be necessary to adjust the script and force the data conversion if necessary.
Cause
This is an intentional change in behavior (introduced in QV 12.20) where the QlikEngine is more effective with identifying, establishing and maintaining date formats. However, this increased awareness assumes that all dates are properly established and that they are a valid interpretation of either a date or the corresponding raw numeric format.
An optimized QVD is simply a mem copy operation and will not affect the original format whereas a non-optimized QVD load requires that the full ETL (Extract Transform Load) steps are performed; which affects performance in a negative way and formatted fields are being recalculated in order to fit with the data model. This recalculation sometimes result in that formatted values revert to the raw format in order to preserve the exactness of the numerical value rather than the format (which can always be modified at a later stage.
The format of an optimized QVD is propagated to a non-optimized QVD load when no explicit numerical format is established using the date() function. The original format of the optimized QVD is now preserved throughout an non-optimized reload of the QVD file if no other formats have been specified. Another implication is that this new behavior is much more deterministic but at the same time less forgiving with implicit formats. As a consequence it is more important to manage (raw) non-formatted values explicit. It is possible to keep the old (raw) non-formatted behavior of the QVD load by using the date() function in all relevant places, but it should be possible to maintain the implicit formats as long as the original data source is managed in a more explicit way.
Internal Investigation ID:
