Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi everybody,
I loaded a simple xls-spreadsheet and follwing errors ocurred though Qlik Sens says the data was loadad correctly:
1. Instead loading the correct date e.g. 24.11.2015 follwing date is loaded: 23.11.2011 ???
2. Not all the lines are loaded, Only a few ones.
I didn't change any parameters, I just went through the standard upload procedure.
Thx in advance for help!
Regards
R.
are you loading the same excel files??
QS is saying that data is loaded correctly? then what is the error?
You might fetching another sheet?
Hi Ricardo,
Is it possible to attach a sample QVF so that I can have a look at it?
Hi Ricardo,
Did the date-field change in lay-out between your normal files and the latest one?
Are there any filters set, which make you could lose all those lines? e.g. if some values are less than or higher than...
If the load is performing as it should, then I would look first at my source data and make sure nothing has happened there.
Kind regards,
Johan
Hi everybody,
thx for replying.
I am fetching the correct sheet.
Today I created a new tab with sample data. The dates where e.g. 21.10.2014. What QS did is putting antoher date in the example from above the 20.10.2011. I don't know why and I don't know how to solve the problem
Best regards
Ricardo
Please post an example source file and qlik sense app that demonstrate the problem. Unless we can see what data you are using and what you're doing to it in the script we won't be able to tell what's going wrong.
Hi,
I found coinsidently the reasen. While creating a sample file it suddenly worked. The only difference in the sample was, that I just had 1 column for a date. In my original file I had two columns next to each other with the same dates. For whatever reason QS wasn't able to load the correct dates. Each column was loaded and had dates but the wrong ones... ??
Whatever... now it works 🙂
Thx for helping!
Hi Ricardo,
Glad you found the solution. As I mentioned before, it was in your source data :-).
KR