Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Woohoo! Qlik Community has won “Best in Class Community” in the 2024
Khoros Kudos awards!
3 Solutions
Accepted Solutions
I think you are missing something in your script, or maybe you don't have access to the file you are trying to load. I did a small sample, and it works without any problem:
Be aware that using // - double slashes - comments out your code. I see you using in your example and I'm not sure if you just mistyped it or not.
Also be careful with variables like this:
Set vFilePath = 'lib://Spazio condiviso MEX:DataFiles/'&$(endYear)&'.xls';
This will not work. You have to use SET only when you are not processing/calculating the variable values - the values are hard coded. In the above case, you have to use LET and you don't need the & to combine the variables inside strings:
LET vFilePath = 'lib://Spazio condiviso MEX:DataFiles/$(endYear).xls';
You can try this exercise, add a TRACE function under your vFilePath tests and see how Set and Let works.
This is my test code:
These are the outputs:
Note when you use Let the vFilePath gets its finished formatted value while with Set you don't.
So, when you use FileSize function without the single quotes and using SET, Qlik is 'calculating' the filename at the moment you are calling the function. Using the LET and with quotes, you are passing the already calculated/formatted filename.
FileSize with single quotes and using Set does not work because the statement gets awkward and Qlik is not able to process it. It is something like this:
FileSize(''lib://Spazio condiviso MEX:MEX_SFTP_PROD/prodotto/'& 2024 &'.xls'')
That is why you get the error:
So, as a general rule, to be safe, use SET for hardcoded values like strings, dates and, numbers. User LET for anything that will be calculated. Like strings concatenation, values returned from Qlik Functions or other variables. By the way, LET also works fine with hard coded values.
I think you are missing something in your script, or maybe you don't have access to the file you are trying to load. I did a small sample, and it works without any problem:
Be aware that using // - double slashes - comments out your code. I see you using in your example and I'm not sure if you just mistyped it or not.
Also be careful with variables like this:
Set vFilePath = 'lib://Spazio condiviso MEX:DataFiles/'&$(endYear)&'.xls';
This will not work. You have to use SET only when you are not processing/calculating the variable values - the values are hard coded. In the above case, you have to use LET and you don't need the & to combine the variables inside strings:
LET vFilePath = 'lib://Spazio condiviso MEX:DataFiles/$(endYear).xls';
You can try this exercise, add a TRACE function under your vFilePath tests and see how Set and Let works.
This is my test code:
These are the outputs:
Note when you use Let the vFilePath gets its finished formatted value while with Set you don't.
So, when you use FileSize function without the single quotes and using SET, Qlik is 'calculating' the filename at the moment you are calling the function. Using the LET and with quotes, you are passing the already calculated/formatted filename.
FileSize with single quotes and using Set does not work because the statement gets awkward and Qlik is not able to process it. It is something like this:
FileSize(''lib://Spazio condiviso MEX:MEX_SFTP_PROD/prodotto/'& 2024 &'.xls'')
That is why you get the error:
So, as a general rule, to be safe, use SET for hardcoded values like strings, dates and, numbers. User LET for anything that will be calculated. Like strings concatenation, values returned from Qlik Functions or other variables. By the way, LET also works fine with hard coded values.
