Participate in Qlik Technical Previews, submit ideas, and review documentation.
Please search for an idea before you post a new one. Your idea may already have been submitted!
Get an early view of upcoming Qlik product releases.
Discussions and related ideation information
Hello everyone and welcome to the new Ideation Discussion Board!
The Product Insight & Ideas blog has been retired and replaced by the Ideation Discussion board. This will allow the Ideation community to all post and comment on discussions related to the Ideation process. The Ideation rules from the original blog were reposted here and pinned to the top.
A few rules before you post:
So, check it out and start posting! I can't wait to engage with you all.
Meghann
Opening a sheet in a browser on a mobile device is 6 seconds +/- faster than opening a sheet using the Qlik Sense Mobile App via QLIKSENSELINK.
This is because the mobile app app executes some activities that the browser doesn't:
Our users do not use the offline capabilities of the mobile app, nor do they use the hub. Our users only use the QLIKSENSELINK mode to access Qlik Sense on a mobile device. We do not need a full list of all apps and streams a user has access to when opening a sheet via QLIKSENSELINK. We only need to know if they have access to the sheet and a license. Perhaps we need a new API that QLIKSENSELINK can call.
We have a requirement in our project that is we need to encrypt log stream data when we are fetching from source system to Log stream staging file. IF this is not possible we need to have TDE support for the Oracle tables(source tables).
Need need addational security for Qlik enterprise manager /Qlik replicate to configure tasks , endpoints to specific groups so the data connections/endpoints and tasks are not exposed to everyone who has access to server . Role Based access needs to be implemented to comply with Sox Audit . Need to restrict data previews for PII etc ..
In Storytelling: when we embed a live sheet in the presentation, titles are displayed but not exported to ppt or pdf. The header displays important, auxiliary information that the users often pays attention at. The users wants to see this information in exported files.
It's necessary the ability of headers exporting to ppt or pdf.
We need to include region as the default parameter value to be included in the task JSON file during the export process. When we export the task we do not see region for US-EAST-1, but this is populated when the region is changed to any region other than us-east-1. I think it is not populating the region for the default value (us-east-1), but we need to include this property by default so that we can the change the region dynamically during the import process in other regions.
Task Endpoint JSON properties in region us-east-1
{
"name": "KineisEndpoint",
"role": "TARGET",
"is_licensed": true,
"type_id": "KINESIS_COMPONENT_TYPE",
"db_settings": {
"$type": "KinesisSettings",
"topic": "Attunity_Kinesis_POC",
"messageKey": "PRIMARY_KEY",
"accessType": "IAM_ROLE"
},
Task Endpoint JSON properties in region us-west-2
{
"name": "KineisEndpoint",
"role": "TARGET",
"is_licensed": true,
"type_id": "KINESIS_COMPONENT_TYPE",
"db_settings": {
"$type": "KinesisSettings",
"topic": "Attunity_Kinesis_POC",
"messageKey": "PRIMARY_KEY",
"region": "US_WEST_2",
"accessType": "IAM_ROLE"
},
When a qliksense object data is exported to excel, user will not be able to identify what selections has generated the data. Hence current selections should be included in exported excel file.
I'm speaking from a QlikView perspective (I can't comment on Sense so don't know if this is / isn't available), but the ability to control the parameters by which an object expands when the end users wishes to expand an object. Currently, this takes over the full page, but I'd like the ability to reduce this size on the page.
Thanks for considering!
Support Partition-Switching for Microsoft SQL Server Endpoints.
The ability to use table partitioning provides faster speeds loading data. Partition Switching improves the performance in archiving very fast. Old data can be switched out to separate tables or purge if necessary. For very large databases, especially OLTP, having the ability to partition-switch provides a fast method of moving table data or purging it with minimal resources required. Most definitely, much more efficient than performing delete ranges or truncating.
Currently, Qlik Replicate User guide has documented the following limitation:
"Partition switching is not supported."
However, by modifying the publication (with the changes listed at the bottom) Attunity replicate will still perform the INSERT/UPDATE/DELETES whether the Attunity task is turned off or in change replicate (using tlog replication). Attunity does perform the replication tasks but provides the following error during partition-switching:
Stream component 'st_0_TaskName' terminated
Stream component failed at subtask 0, component st_0_TaskName
Error executing source loop
Endpoint is disconnected
Encountered an unexpeceted error
... and here we can get an idea why the error was triggered:
Failed in applying table mapper catch up.
mssql_table_mapper_catch_up(...) failed in performing CATCH_UP statement 'select s.partition_id,s.object_id from sys.system_internals_partitions s , sysobjects o where s.object_id= o.id and o.xtype=N'U' and s.is_data_row_format=1 and s.object_id in (1841493689 )'
-- modifying the publication to allow partition switching in transactional replication
EXEC sys.sp_changepublication
@publication = @publication,
@property = 'allow_partition_switch',
@value = 'true';
And
EXEC sys.sp_changepublication
@publication = @publication,
@property = 'replicate_partition_switch',
@value = 'false';
Additional benefits:
1) We archive our replicated databases (at publisher/distributor) having different retentions - improving performance and recovery.
2) Ability to reload subscribers from specific partitions
3) Ability to purge at the source (OLTP) - let's say 90 days, and still retain entire history at the landing/replicated database.
4) Ability to replicate any INSERT/UPDATE/DELETES until records have been partition-switched (90 day retention for example).
5) High performance, minimal-locking, and minimal resources utilized in archiving/deleting large number of records.
We are using Replicate with a MongoDB Source and an Oracle Target.
We would really like the AR_H_COMMIT_TIMESTAMP/AR_H_TIMESTAMP header columns to be populated with a timestamp value that has greater precision than a second.
Other sources populate those columns down to the millisecond, but it only goes down to the second with a MongoDB Source.
The MongoDB Oplog does contain a commit timestamp field that has the greater precision, but the current one that is being pulled from the Oplog only goes down to the second.
Hi guys,
I really miss the "inputfield" functionality that was available in QlikView to do small whatif's inside tables and to be able to do much more precise calculations than what ifs we do now with generic variables.
Do you have in the roadmap integrate the inputfield in Qlik Sense?
For me it is a very important must.
Regards, Marcel.
One problem I see with some of our NPrinting customers is the need to install NPrinting Designer locally.
Many customers no longer work locally, but via Terminal Server, Citrix or ThinClients.
This makes it difficult to use the NPrinting Designer. The problem of having only one instance of the Designer on a terminal server does not make it any easier.
Hence the idea to check if it is possible to develop the Designer web-based? Qlik Sense can also be used entirely in the browser, this approach should also be applied to NPrinting.
I am aware that MS Office locally might be a sticking point here, but I think Qlik has many smart developers who will surely find a good way to implement it.
I am working on a new Qlik Sense Enterprise & Nprinting implementation. This organization does not use Microsoft Office products.
I've been asked about the potential for integration with Google's office products (G-suite) in both Qlik Sense and Nprinting. In Sense, it's mostly about Stories and data exports. I can work around it.
Nprinting is even more tightly integrated with Microsoft Office products in terms of design: Word, Excel, PowerPoint. When I I am discussing or demonstrating Nprinting within the company, I am often asked about integration with the G-suite products we use: Docs, Sheets, Slides.
Several of my smaller clients in the past have also asked about G-suite possibilities when discussing Qlik.
In NPrinting there is the possibility to import users via Excel. Changes can also be entered in this way.
The problem is that as soon as a change is made in the web console and Excel is then imported, the previous change is of course deleted.
The same with changed passwords
-> Initial password is read in via Excel
-> User changes the password in the console
-> Excel is loaded again and writes the "old" password
Therefore, it should be possible not only to import but also to export the user information, so that other changes are not lost.
There's a great set of Monitoring Apps for Qlik Sense Enterprise on Windows but there's no parallel on Cloud Services - all you get is a basic list of user activity in the Console.
Some of the APIs used by the Monitoring apps are also available in the cloud but the log files / database aren't.
A version of the apps using purely the APIs would be useful especially for pure cloud deployments.
QlikSense NPrinting- more detail level understandable log details like normal Qliksense logs as changing to debug option not help much. We also want to see the exact error in Log where it stuck if keep on running.
I already tried debug option enable here as per below article, but this doesn't help
Hi,
The idea is to extend or display the existing XRControls in the PixelPerfect Designer.
Currently the DevExpress libraries are by far outdated (more than 6 years) but there is an particular Object XRControl that could be at least be available for use in the current version:
XRPivotGrid
The option to bind a chart to a pivot grid is even displayed in the current designer:
It would be available in the Standard Controls Tool Box:
A powerfull pivot table creator that could save many developers lives and time...
The PixelPerfect is such a powerfull template editor. But in Qlik NPrinting it is sadly handicapped.
Source: https://docs.devexpress.com/XtraReports/DevExpress.XtraReports.UI.XRPivotGrid?v=17.2
Partner
1176Luminary
430Creator III
281Employee
175Luminary
168Partner
155Partner
150MVP
131Digital Support
130Creator
111