Boa tarde pessoal!
Gostaria da ajuda de vocês, estou trabalhando numa informação de Clientes Recuperados, ou seja, clientes que estavam a mais de 12 meses sem comprar, mas que voltaram a comprar no mês atual (Mês de análise). Utilizei o método abaixo para marcar os clientes inativos, porém não deu muito certo, me trouxe apenas resultados de jan, fev e mar 2024 ↓↓↓

ClientesInativos:
LOAD
PedidoVendaCódigoCliente,
1 as PedidoVendaIndicadorInativo // Marca clientes que estavam inativos
Resident UltimoPedidoTotal
Where Monthstart(PedidoVendaUltimaDataFaturamentoPedido) < Monthstart(AddMonths(Today(), -12));

What's your experience? Share with the Community and earn the **new** Agentic AI Expert badge.

You've moved past the first try. Now tell us what happened when agentic AI stopped being an experiment and started being part of how you actually work.

Post your experience here and we'll award you the Agentic AI Expert badge.

Tell us in the comments:

• What result or takeaway can you share?
• Do you have a metric or success story? For example, time saved, faster answers, fewer manual steps?
• How did you (or how do you plan to) expand this beyond a one-off experiment into a regular workflow?
• Got a screenshot? Share it if you can. Seeing the real thing helps everyone else picture it in their own environment.

Bonus: tag a colleague who should be trying this too. By sharing your experience, you help inspire others and generate ideas in the Community.

Everyone who shares their experience here gets the Agentic AI Expert badge.

Thank you for taking the time to share!

So we trying to load data in s3 bucket in CSV format but i can see dates are not getting populated in CSV soo i have applied global rule but than it is changing the date 

1 transformation rule 
Transformation

Transformation Scope

Transformation Action

Hi all,

I have a DB2 for z/OS source endpoint on Qlik Replicate configured with SSL. Today, tasks connected to this endpoint have been failing with the following error:

SQL30081N A communication error has been detected.
Communication protocol being used: "SSL".
Communication function detecting the error: "sqlccSSLSocketSetup".
Protocol specific error code(s): "446"

The DB2 team confirmed that there had been changes to the SSL certificate on the mainframe side, and provided us with the updated certificate to install on the client side, where Qlik Replicate is running.

Could someone help me understand:

• How do I replace/update the certificate in the existing keystore, without having to recreate it from scratch?
• After updating the certificate, is it necessary to restart the entire Qlik Replicate Server service, or is it enough to stop and restart the individual task?
• There are other active tasks connecting to the same DB2 endpoint that are currently still working (likely because their connection was established before the certificate change) — do I need to be careful about those when applying the change?

Thanks in advance to anyone who has dealt with a similar situation!

Get started. It's easier than you think

Here's the good news: agentic AI capabilities are already sitting inside Qlik Cloud. Many of our Community members can start extending what you already do with Qlik right now.

A few places to start:

• Set up the MCP Server and connect Qlik to the AI tools you already use
• Try Qlik Answers and ask a question in natural language
• Explore Discovery Agent and let it flag the anomalies you'd otherwise dig for
• Check out Data Products for a faster path to reusable, governed data

None of these need a rebuild of your analytics environment. They build on the governed data you've already invested in.

Tell us in the comments:

• Have you toggled on any agentic capabilities yet?
• If yes, where have you started, and was it easy? Tell us your observations.
• If not yet, what's holding you back? Questions about setup, security, or where to even start all count. Ask it here.

Once you've activated something, head over to the next post and tell us what you’ve built.

Once you've activated agentic AI capabilities, it's time to put them to work on something real, even something small.

Post your use case or workflow ideas here and we'll award you our newest Qlik Community badge: Agentic AI Adopter.

Tell us in the comments:

• What are you exploring? (Forecasting, anomaly detection, natural-language Q&A, something else entirely?)
• What did you build, or what are you planning to build?
• What's your top tip for a fellow Community member trying this for the first time?

A few ideas if you're staring at a blank page:

• Ask Qlik Answers a question you'd normally build a whole sheet to answer
• Point Discovery Agent at a metric you check every week and see what it surfaces
• Create a Data Product within Qlik Analytics

This doesn’t need to be polished. A simple “I tried this, and here’s what happened” works just fine!

Everyone who posts a first workflow, use case, or related project planning here gets the Agentic AI Adopter badge to display on your profile. 

Hi everyone,

I am facing a critical security concern regarding Section Access and Binary Loads, and I would like to know if there is a way to prevent it.

The Scenario: I have a base application with Section Access properly applied to restrict data visibility. Another developer user consumes this app's data model using a Binary Load.

The Problem: The issue happens when this developer uses the STORE statement in their script to export the loaded tables into QVD or TXT files. The exported files are created without any access restrictions. The Section Access rules are completely bypassed in the stored data.

The Security Concern: Because of this behavior, a developer can easily extract restricted data into unrestricted files. I consider this a severe security risk and data leakage problem, and I am very concerned about the platform's data governance in this scenario.

My Questions:

1. Is there any way to block, disable, or restrict the use of the STORE command for developers who are using a Binary Load?

2. Are there any configurations, security rules, or best practices at the QMC/Tenant level to prevent this specific type of data extraction?

I understand that we could segregate access using Spaces. However, these developers need to access the data spaces to perform the Binary Load and consume the data model. Even if we restrict their write access to corporate Shared/Data Spaces, they might still be able to STORE the data into their Personal Spaces. How do you handle this architectural dilemma without completely stopping the use of Binary Loads?

Any insights or workarounds to secure this architecture would be greatly appreciated.

Thanks in advance!

Hi there,

Is there an API we can use as an admin (using region AP OAuth credentials) to set the 'Default notifications' for a user we create programmatically?

I can't seem to find it (or I'm not looking in the right place!) - ideally we'd like to be able to enable/disable each of the tick boxes per method and per type.....

It's frustrating that when users are added to a space (directly) they, by default, receive notifications around invitations to new content etc. in an OEM environment - perhaps this can be disabled by default in OEM environments?

Thanks,

Lachlan

We have a busy source table and have lots of transaction every minutes. However we don't see the table gets replicated under CDC into target. Source is MySQL 8.0.45 on premise while target endpoint is Snowflake AWS.

We have enabled target apply to verbose however it's not showing up as target apply in the logfiles. It only has source_capture.

23898836: 2026-09-15T12:17:52:393625 [SOURCE_CAPTURE ]T: Event header: type=16, timestamp=2026-09-15 12:17:52 (1789489072), event_len=31, pos=1069454637, next_pos=1069454668 (mysql_endpoint_capture.c:1195)
23898836: 2026-09-15T12:17:52:393625 [SOURCE_CAPTURE ]V: Event = 16, file_suffix=8666 (mysql_endpoint_capture.c:3072)
23898836: 2026-09-15T12:17:52:393625 [SOURCE_CAPTURE ]V: Resuming=0, EventPosInFile=1069454637, EventHeaderNextPos=1069454668 (mysql_endpoint_capture.c:3097)
23898836: 2026-09-15T12:17:52:393625 [SOURCE_CAPTURE ]V: Event timestamp '2026-09-15 12:17:52' (1789489072), pos 1069454637 (mysql_endpoint_capture.c:3148)
23898836: 2026-09-15T12:17:52:393625 [SOURCE_CAPTURE ]T: > XID_EVENT (mysql_endpoint_capture.c:3201)
23898836: 2026-09-15T12:17:52:393625 [SOURCE_CAPTURE ]V: Send COMMIT (7) record, record id -1795445488, stream position '$.008666:1069454637:-1:1069454668:37221256041509:$.008666:1069454456' (mysql_endpoint_capture.c:3722)
23898836: 2026-09-15T12:17:52:393625 [SOURCE_CAPTURE ]V: read_next_binlog_event: next_pos=1069454668, curr_file=LUSQTTNDB04A-bin.008666, curr_file_len=1069454668, last_file=LUSQTTNDB04A-bin.008666, last_len=1069454668 (mysql_endpoint_capture.c:973)
23898836: 2026-09-15T12:17:52:393625 [SOURCE_CAPTURE ]V: Wait for new events... (mysql_endpoint_capture.c:981)
23898836: 2026-09-15T12:17:52:409223 [SOURCE_CAPTURE ]T: Wait minimum 5 seconds for next poll (mysql_endpoint_capture.c:994)

We're challenging our Qlik Community: put agentic AI to work. 

We saw lots of great posts in our recent Make Your Data Work for AI forum. We’re building on that momentum with a new board focused on the next step: driving real impact with agentic AI.

This is the place to get started with agentic capabilities, try them out, and share your experience with the rest of the Community.

Here's the challenge:

1. Get started. Toggle on Qlik Answers, activate Qlik’s MCP Server, or get started with whichever capability fits your work, and see how easy it really is.
2. Build your first workflow. Identify a use case and put the capabilities to work on a real problem or task.
3. Share your experience. Tell the Community what you learned, what worked, and what surprised you.

Ask questions, share screenshots, get ideas, and help your Qlik Community peers on their journeys.

You'll earn NEW Community badges along the way: Agentic AI Adopter when you share your first workflow or use case, and Agentic AI Expert when you share your learnings and results.

Plus, we’ll be awarding some fun surprises and new Qlik swag along the way!