Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello, I've an error using the Reporting Option in Qlik Cloud that I don't manage to understand.
My report need to be sent to one user and doesn't need a specific Filter.
Si
I'm loading a Sample.xlsx file with only one user and a "fake" filter called TOTO
In the Filters menu of the Reporting option in Qlik Cloud, I've added Filer called TOTO
In my Script I've this dummy table not linked to anything in the qvf file.
LOAD * INLINE [
TOTO
TOTO
];
Each Time I start the report generation I get an error :
Error in reporting service dependency
Error code: SHA-10000
Trace ID: 0e62e9312cd7bf8edbf2184bbfbf4d6b
Details: Filter FieldName not found or renamed in the App
Filter: TOTO
Email: mymail@mailbox.com
I don't manage to understand what causes this error.
Can someone helps me ?
Regards
Using the recipient import file to import filters directly from the app does not work.
The import file only enables you to 'identify' or 'map' to the filter that is created as a filter under the 'filters' section of the Qlik Reporting interface.
However, to create a filter in Qlik reporting, the dimension and dimension value need to exist in the app.
So check:
1. does the app contain the dimension and value that you want to use as a filter in Qlik Reporting
2. have you manually created the filter in Qlik Reporting with this information from the app.
The following link describes the process.
Also the inline table should be associative with the rest of your app data. Ie: it should be linked to the main fact table.
Kind regards...
Hello,
Thanks,
1. does the app contain the dimension and value that you want to use as a filter in Qlik Reporting => Yes
2. have you manually created the filter in Qlik Reporting with this information from the app. => Yes
Link https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Reporting/cloud-in-app-r... => Check (/) : it's already what I do
Also the inline table should be associative with the rest of your app data. Ie: it should be linked to the main fact table. => I've added a link (to every information of the main fact table because, In fact, I don't want to use a filter for each, it's just it seems to be mandatory).
I've removed Section access.
Every time I launch report I've this error :
Error in reporting service dependency
Error code: SHA-10000
Details: Filter FieldName not found or renamed in the App
It's as If Qlik Reporting don't manage to link the name of the Filter from the Sample.xlsx file and the One in Reporting / Filters.
I've tried a huge number of things :
- Remove Section Access.
- Copy Paste the name between the Sample.xlsx and Fillter in reporting.
- Checking hidden space before / after the name of the filter.
- Suppress the Sample.xlsx in the data space and suppress the automatic created page in Load Script (Distribution List).
- Use a blank filter in the Filter cell of the Samples.xlsx
- Reset the Samples.xlsx file
- Use the same Name as Field / Value / Filter Group Name
=> it Still doesn't work
Any other idea ?
It seams to be a problem with your load inline statement then.
Please follow this for load inline formatting. Below is just one example of many.
Examples - Inline loads with transformations
Thanks for your suggestion, the problem is not from the inline instruction
Since your previous suggestion, I'm now using a table :
user_filter_bidon:
LOAD Distinct
date.year, // link to the main data
'bidon' as champs_bidon // field to select to have a useless filter for user
Resident
date;
I suspect this is a bug.
I've created a ticket on the support
Did this get fixed? I am running into a similar issue.
Hello, not directly.
The support proposed me a workaround (let the filter column empty) which was working in my particular case. But I'm sure there was some kind of bugs somewhere.
I would advise you to create a ticket to the support on your case.
Regards
Hi,
I got the same message,
Error in reporting service dependency
Error code: SHA-10000
Since, did you fixe it ?
Regards,
Koala23
was there a bug number for this issue that you got from qlik support?