Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Getting below error while trying to do restoration
There are 37 other sessions using the database.database "QSR" is being accessed by other users.
Can we configure a friendly 'From' name with the Mail block in QAA? Instead of just an email address
Perhaps adjusting the headers using the Custom code block?
i.e. "John Doe <j.doe@website.com>"
Hi, I have been trying for a couple days to solve the JVM compatibility error.
I get the error when I try to run a job from my imported Talend workspace.
The Java I have installed is of version 11. The compiler is set to 1.8 by default.
I've tried several things:
- Modifying a configuration file of Talend and then adding a Java path as well.
- Getting third party modules to see if it would help resolve the error.
- Reinstalling Java and Talend. I also tried different versions, such as 8 and 22.
I've also tried different solutions that I could find online but none of them seemed to work.
Please help, I can also supply more information if needed.
Kind regards,
J.
I am new to administration for Qliksense. I published an app from Dev (QMC2) into Prod (QMC) which overwrote it. That was the wrong app so I am being told to revert back to the previous version of the app. How can I do that? Is it possible?
On May 7, 2024, we will push a change to Qlik Cloud Analytics that will add a new safeguard for apps containing section access tables.
Background:
It is currently possible to specify up to 1 000 000 distinct values per user for the reduction and OMIT fields. After reaching 1 000 000, the table is truncated.
As of now, there is no indication that the truncation happened. Users might make business decisions based on an incomplete or incorrect set of data without realising that. This a rare scenario, given the large number of values, but we want to prevent this from happening.
What will change?
During the reload of apps, we will execute an additional Section Access evaluation: if the number of distinct values in either the OMIT or any reduction field per table exceeds the number of 1 000 000, the reload will fail. Currently reloads are succeeding without any indication of the truncation.
Why the change?
This is a safeguard to prevent users from getting a truncated section access table when viewing the data, preventing them from seeing too much, or too little.
How can we recognise Section Access evaluation from standard reload failures?
Errors related to Section Access evaluation failures will look like this:
Error during section access evaluation. Field (NAME_OF_THE_FIELD) contains 1000002 unique values. Max allowed is 1000000 unique values.
Is the new safeguard stricter than before?
Yes. The new safeguard is stricter: 1 000 000 unique values per table as opposed to the 1 000 000 unique values per user of the standard Section Access limitation.
There are reasons for this: adding per-user evaluation would cause a performance impact on reloads, and having stricter safeguard will allow administrators to keep an eye on apps that are at risk of showing an incorrect set of data.
Will some of the reloads that are currently safe within the limit fail?
Yes. Because of the stricter guardrail, a very limited set of reloads that are currently showing data as expected will fail. Qlik Support will reach out via proactive cases to customers who are currently in that scenario according to our logs. However, we encourage every customer to review section access tables with a large number of values that are currently at risk of being truncated.
Can we go back to the old behaviour?
Yes. To disable this evaluation in a particular script, add “SET EnableSectionAccessEvaluation = 0”; to the script. This variable can already be added before the change is in place, without impact on current reloads. Adding the variable will revert to the old behaviour, where reloads succeed ad section access distinct values are truncated after the limit of 1 000 000 per user.
Note: Disabling this evaluation carries the risk of getting a truncated section access table for particular users after a reload, which is what we aim to avoid with the new safeguard.
Qlik Replicate opens 4 connections to the target. I know why 2 of them are used.
1 connection is used for appling changes, the second connection is used to get meta data of tables from target.
But why 2 rest connections are established to the target, I do not understand. Monitoring shows that nothing goes through them.
If versioned DBMS is using (Sybase IQ in our case) it is very important that there are no such idle connections, because they lock deleting old versions , and it may lead to run out of space.
Please tell me why 2 more connections are connected to the Target? Is it possible to kill them so they don't accumulate versions??
Hi Team.
We are currently using Oracle 19.21 as a source and Microsoft Azure Event Hub as a target with the default task settings. However, we have observed a relatively low throughput of around 1500 forfull load and CDC Task.We are seeking guidance on any adjustments we can make to the settings to improve the replication process's speed.
Regards,
Chirag Patil.
We are connecting to ProgressDB using ODBC DSN, Connection was implemented successfully.
When we are trying to get the table details we are getting the below error.
SYS-E-HTTPFAIL, Command get_owner_list failed when getting the list.
SYS,GENERAL_EXCEPTION,Command get_owner_list failed when getting the list.,Failed to get owners '' RetCode: SQL_ERROR SqlState: 08S01 NativeError: 0 Message: [DataDirect][ODBC Progress OpenEdge Wire Protocol driver]Unexpected Network Error. ErrNum = 10054
Do we have to give any particular access, the user has access to all the tables in Progress DB.
Hi everybody,
In case there is anyone with some relevant experience in connecting to ODOO data and getting it into Qlik (Cloud, most likely, (but any other option , like Sense on-prem or even QlikView, can become relevant, as well), we are open to employ & REWARD this experience, once proven!
We are searching not only the know how of properly defining the connector, but also in identifying the right tables/joins/filters/dimensions and measures for various Odoo modules. (First targeted modules are around Sales & GM% analytics)
Feel free to PM me or email me (cotiso@qqinfo.ro) !
Sempre fi,
Cotiso
I have been trying to embed qlik sense into an eternal angular app, for getting the app list we have been using the below api
https://172.22.18.153/qrs/api/v1/items?resourceType=app.
it is resulting in the following error. XSRF prevention check failed. Possible XSRF discovered.
The solution to this problem is given as incluing xrfkey to the url,the xrfkey in the URL should match the xrfkey in the api header right ??
How can i get the xrfkey??
Wondering about Qlik Talend Data Integration Sessions? There are 11, in addition to all of the Data & Analytics. So meet us in Orlando, June 3 -5.
Browse our helpful how-to's to learn more about navigating Qlik Community and updating your profile.
Join us on April 24th at 10 AM ET for the next Do More with Qlik webinar focusing on Qlik’s Data Integration & Quality solutions.
Your journey awaits! Join us by Logging in and let the adventure begin.
Qlik enables a frictionless migration to AWS cloud by Empresas SB, a group of Chilean health and beauty retail companies employing 10,000 people with 600 points of sale.
Qlik Luminary Stephanie Robinson of JBS USA, the US arm of the global food company employing 70,000 in the US, and over 270,000 people worldwide.
Join one of our Location and Language groups. Find one that suits you today!
A private group is for healthcare organizations, partners, and Qlik healthcare staff to collaborate and share insights..
Qlik Communityの日本語のグループです。 Qlik製品に関する日本語資料のダウンロードや質問を日本語で投稿することができます。
Welcome to the group for Brazil users. .All discussions will be in Portuguese.
Hear from your Community team as they tell you about updates to the Qlik Community Platform and more!