The Qlik Application Automation JIRA blocks List issues, List issues by project and List new and updated issues incrementally, have been updated to the latest API URL.
The changes come into effect on the 1st of May 2025.
What has changed?
The following changes in the blocks:
Input Parameter changes
List issues block:
Current (Old) Version:Input parameter "Jql"is optional
New Version:Input parameter"Jql"is a required parameter
List issues by project:
Current (Old) Version:Input parameter "Project" is optional
New Version:Input parameter "Project" is a required parameter
List new and updated issues incrementally:
No changes
Response changes
Old Response:By default, all navigable fields are returned.If a list of specific fields should be returned, specify the names of the fields in the "Fields" input parameter.For an example of the raw response, see the attached .json (JIRA-old-response.json) file.
New Response:By default, the resource returns IDs only.If a list of specific fields should be returned other than “id”, specify the names of the fields in the "Fields" input parameter.Example of the response:
[{"id": "157638"},{"id": "156647"}]
Example of the response if a user has specified the names of the field (such as "Summary") in the "Fields"input parameter:
[{"expand": "","fields": {"summary": "Main order flow broken"},"id": "10002","key": "ED-1","self": "https://your-domain.atlassian.net/rest/api/3/issue/10002"}]
How do I prepare for the change?
Update your automations to use the new updated blocks:
Select the old block
Then click Upgrade to latest versionFollow the same steps for all remaining blocks, such as List issues by project and List new and updated issues incrementally.
Since the response has been updated, the "Id" field will be returned by default if no fields are specified in the "Fields" input parameter.After upgrading any of the List issues, List issues by project, and List new and updated issues incrementally blocks, add the relevant fields to the input parameter in the block, which is referenced by other blocks.
Additionally, modify the output references in other blocks if necessary. If this is not done, it will result in a null value for the input parameter, causing referenced blocks to fail with the error "Missing mandatory parameter" whenever the input parameter is required.Example error:{ "response": { "status": 400, "body": { "errors": [ { "code": "HTTP-400", "title": "Invalid Request.", "detail": "Missing mandatory parameter \"Summary\"." } ] } }, "external error": false }
If you have any questions, we're happy to assist. Reply to this blog post or take similar queries to the Qlik Application Automation forum.
Thank you for choosing Qlik, Qlik Support
...View More
The Qlik Application Automation HubSpot block Get Contact by Emailhas been updated to the latest API version, pointing it to HubSpot v3 API.
What has changed?
Input Parameterchanges
The new version changes how input parameters are handled. While the current (old) block returns all properties by default, the new block requires explicitly specifying the fields you need.
Input Parameters available in the old (current) block:
Email
Input Parameters available in the new block:
Email
Properties
Properties With History
Associations
By default, it will only fetch data as shown in the example below. If additional details are required, input parameters like Properties, Properties With History, andAssociations must be added.
Default example:
{"id": "1","properties": {"createdate": "2021-07-27T13:13:25.669Z","email": "emailmaria@hubspot.com","firstname": "Marino","hs_object_id": "1","lastmodifieddate": "2023-07-27T23:18:09.664Z","lastname": "Johnson (Sample Contact)"},"createdAt": "2021-07-27T13:13:25.669Z","updatedAt": "2023-07-27T23:18:09.664Z","archived": false,"key_values": {"createdate": null,"email": null,"firstname": null,"hs_object_id": null,"lastmodifieddate": null,"lastname": null}}
Response changes
Top-Level Structure Differences:
Old Response:
Uses "vid" as the contact identifier.
Contains "canonical-vid" and "merged-vids" for tracking multiple contact records.
"portal-id" is included to indicate the HubSpot account.
New Response:
Uses "id" as the contact identifier instead of "vid".
Omits "canonical-vid", "merged-vids", and "portal-id".
Properties Structure:
Old Response:
Each property has "value" and "versions" fields to track changes over time.
"versions" include timestamps, sources, and previous values.
New Response:
Properties are flattened, storing only the latest value under "properties".
Historical values are now under "propertiesWithHistory", making the structure more modular.
Timestamp Format:
Old Response: Uses Unix timestamps (e.g., "1627391605669").
New Response: Uses ISO 8601 format (e.g., "2021-07-27T13:13:25.669Z"), making it more human-readable.
Data Organization:
Old Response: Mixes computed, user-set, and system-set fields within "properties", making it harder to distinguish sources.
New Response: Separates historical data into "propertiesWithHistory", improving clarity.
See the attached.JSONfiles for comparison responses between the old (hubspot-old-get-contact-by-email.json) and the new(hubspot-new-get-contact-by-email.json) block.
How will this affect me?
If you currently use the HubSpot connector'sGet Contact by Emailblock and do not upgrade it to the new version, the block will stop functioning onMay 30th, 2025.
How do I prepare for the change?
Update your automations to use the newGet Contact by Emailblock:
Select the old block
Then clickUpgrade to latest version
Since the response has changed, modify the output reference in other blocks once you have upgraded the Get Contact by Emailblock. Failing to do so will lead to an input parameter with a null value and cause referenced blocks to fail with the error "Missing mandatory parameter" wherever the input parameter is mandatory.Example error:
{"response": {"status": 400,"body": {"errors": [{"code": "HTTP-400","title": "Invalid Request.","detail": "Missing mandatory parameter \"id\"."}]}},"external error": false}
If you have any questions, we're happy to assist. Reply to this blog post or take similar queries to the Qlik Application Automation forum.
Thank you for choosing Qlik,Qlik Support
...View More
We are introducing a breaking change to the behavior of file paths returned by the DataFiles connector to Qlik Sense.
This update is designed to align DataFiles with the web storage provider connectors. This will better align the DataFiles connector's behavior with other connectors, such as S3, which return folder names with a trailing slash for the DirList argument in loops.
Other web storage provider connectors are not affected.
What's changing
Current Behavior
When using the DirList function with the DataFiles connector, the returned folder path does not include a trailing slash.
New Behavior
With the upcoming update, the DirList function will now return folder paths with a trailing slash—matching the behavior of other storage connectors like S3.
This change is part of our ongoing efforts to support file hierarchy enhancements introduced in Q4 2024 and to ensure consistency across all connectors.
How does this impact your Qlik Sense load script?
The change will primarily affect loops or code configurations that rely on the specific behavior of the output from aDirList argument when processing directory paths. Customers who have implemented custom filtering logic based on the absence of a trailing slash may need to adjust their scripts.
Example script:
// List out the response from DirList as DirFor Each Dir in DirList('lib://DataFiles/')ShowThePath:LOAD'$(Dir)' as PathAutoGenerate 1;Next;
Before the ifx, this will return:
Path
lib://DataFiles/directory1
lib://DataFiles/directory2
Post-fix, this will return:
Path
lib://DataFiles/directory1/
lib://DataFiles/directory2/
What scenarios are unaffected?
Customers using other file listing or filepath functionsare not expected to experience any impact.
Most standard code configurations remain unchanged.
When will the change be rolled out?
The update will be rolled out to all Qlik Cloud tenants onMarch 25th, 2025.
Qlik Cloud Government tenants will receive the update byMarch 25th or later.
Thank you for choosing Qlik,Qlik Support
...View More
Hello Qlik Admins,
The release of QlikView 12.100 IR has been moved to the fall of 2025.
Because of the release date's move, support for previous versions will be extended accordingly:
12.80 will be supported until the end of October 2025
12.90 will be supported until the end of October 2026
Further updates with the exact release date will be provided later in the year.
Thank you for choosing Qlik,Qlik Support
...View More
Hi everyone,
Want to stay a step ahead of important Qlik support issues? Then sign up for our monthly webinar series where you can get first-hand insights from Qlik experts.
The Techspert Talks session from March looked at Embedding Qlik Analytics in SharePoint.
But wait, what is it exactly?Techspert Talks is a free webinar held on a monthly basis, where you can hear directly from Qlik Techsperts on topics that are relevant to Customers and Partners today.
In this session we will cover:
Review of important Qlik Cloud settings
Building the authentication script
SharePoint site integration
Click on this link to watch the recording.
...View More
Within Qlik Cloud Analytics, the Data Alerts feature offers users the ability to be notified of exceptions in the data. When scheduling a data alert, users can define the data conditions of interest within an app and have the option to configure a schedule setting when data is refreshed by a reload of the app.
There will be an improvement to this specific Schedule configuration setting in an upcoming release scheduled for the second half ofMarch 2025.
New to Data Alerts?
Read more in Monitoring data with alerts.
How Data Alerts currently work:
Currently, the schedule configuration When data is refreshed(fig 1) by a reload of the app is evaluated every time the app is reloaded regardless of whether the data set within the app has changed.
fig 1
This has led to users receiving repetitive alerts for the same data status and risks "alert fatigue". It is also not the intended behavior of the feature as no alert should be sent if the underlying data set has not actually changed.
What changes?
With the upcoming change to the Data Alerts feature, the underlying evaluation behavior for this schedule configuration (When data is refreshed by a reload of the app) will be optimized to evaluate only when there is new data available in the app and the app is reloaded. The same alert status may still be sent for a given condition, but the condition will always have been evaluated from a new data state in the app.
What impact will this have?
The impact of this change will reduce the number of alerts delivered to users in the scenario that the underlying data has not changed (on a reload), making the alert delivery more impactful. Of course, users can still use the configuration Compare with: Last evaluation(fig 2) to further optimize their alert delivery.
fig 2
Users who prefer a reload-triggered and repetitive (same data state) data alert might consider:
Change the data alert configuration to a Fixed Schedule
In the case of system app monitoring, configure a notification on the app to communicate when the app is reloaded (App > Notification settings)
Consider using Subscriptions on a scheduled basis to deliver the state of the data
Thank you for choosing Qlik,Qlik Support
...View More
Starting March 11th, 2025, Slack will enforce changes in their APIsaffecting file uploads. To accommodate these breaking changes, we have introduced new blocks in the Slack connector for Qlik Application Automation.
What blocks are affected?
Upload File To Channel (new version)
Send Text Based file (new version)
Send Binary File (deprecated)
What exactly is changing for Qlik Application Automation?
The Send Binary File block will be deprecated. Instead, use the Upload File to Channel block to upload binary files. If you still want to send a base64 encoded string, use the Send Text Based File block and configure the encoding parameter to base64.
The Upload File To Channel block and Send Text Based File block need to be updated to a new version.To perform this update, replace existing blocks with new blocks by dragging the blocks from the block library.
What will I need to do to mitigate this?
Any automation using affected blocks needs to be updated.
SeeBreaking changes for file support in the Slack connector: new blocks introducedfor steps and details.
Thank you for choosing Qlik,Qlik Support
...View More
The following connectors will be removed and are not recommended for further use:
Amazon S3 Metadata
Amazon S3: this is a “File location” connector
Instead, use the following connectors:
Amazon S3 Metadata V2
Amazon S3 V2: this is a “File location” connector
The connectors labeled with the suffix “V2” were introduced in 2022 and have since then been the recommended connectors for access to Amazon S3 buckets.
The V2 connectors access Amazon S3 buckets based on the AWS SDK for .NET Core, whereas the legacy S3 connectors were based on the REST API.
The plans to remove the legacy S3 connectors are as follows:
Qlik Sense Cloud: by the end of April 2025
Qlik Sense Enterprise on Windows: release May 2025
Qlik Web Connector (standalone): release June 2025
The legacy S3 connectors and the S3 connectors “V2” have the exact same capabilities, and a migration will in most cases only require a new connection definition and an update in the connection name within the Qlik Script.
Additional Reading
Data sources in Qlik Cloud Analytics
Built-in Qlik Web Connectors
Qlik Web Connectors
If you have any questions, do not hesitate to contact us through the Qlik Customer Portal.
Thank you for choosing Qlik,Qlik Support
...View More
