Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I'm experiencing a pesky error when trying to load a single portion of a multi-dataset load script. It's a "Field '<fieldname> not found" error which always refers to the first line of this specific dataset - no matter what the field name is.
So when the script says:
LOAD 'filename',
'psrf_UID'
'loaded_at',
...
[dataset_name]:
SELECT 'filename',
'psrf_UID'
'loaded_at',
...
--------
I get this error:
The following error occurred:
Field 'filename' not found
The error occurred here:
[dataset_name]:
SELECT 'filename',
'psrf_UID'
'loaded_at',
...
---------
And when I switch the order of the field names...
LOAD 'loaded_at',
'filename',
'psrf_UID',
...
[dataset_name]:
SELECT 'loaded_at',
'filename',
'psrf_UID',
...
I'm met with:
The following error occurred:
Field 'filename' not found
The error occurred here:
[dataset_name]:
SELECT 'loaded_at',
'filename',
'psrf_UID',
...
-------------
I've checked all the field names; they exist and are spelled correctly. My connection string appears on the line before the LOAD statement (followed by a semicolon, of course).
This load script has several different datasets, and when I comment out the problematic code above, the load script runs smoothly. If I change the order of the datasets in the load script, it always errors out on the same dataset.
Any ideas? This is driving me mad!
I notice you are mixing the use of "LOAD" AND "SELECT", do you have different types of data sources? From which data source do you have trouble?
What happens if you only load one data set?
I notice you are using single quotes. That is often interpreted as string values by Qlik. Consider changing to this:
LOAD [loaded_at],
[filename],
[psrf_UID],
Can you share screenshot of your script.
try
Load *;
SQL Select * from .....
instead of fieldname write * & try.
Regards,
Prashant Sangle
Thank you for your response. I am loading a script using an Apache Spark data connection. Other datasets from this connection load just fine (including those with the quote marks in the SELECT statement). It still doesn't load even if it is the only dataset in the script.
The issue might originate with the data source I'm trying to load from, but on its face it appears to be almost identical to another dataset in my script which loads just fine. I'm not sure what to look for in the original data source that would cause this error.
The single-quote wrapping of the field-names within the load-part is wrong respectively invalide. Within the sql select it may be valide because this part isn't executed from Qlik else transferred to the data-base and must fit to their syntax.
Field-names without a special char like +- and without spaces don't need mandatory a quoting and you may skip it. Valide quotes for the field-names would be "Field" or [Field] or `Field`.