Release date:
🍾 Happy New Year Everyone! 🍾
We’re excited to kick off the year with a brand-new Wiiisdom Cloud Platform version!
Let’s dive into what’s new!
As always, you can find important links just below.
Full Documentation: Wiiisdom Cloud Platform Documentation
Knowledge Base: Wiiisdom Cloud Platform Knowledge Base
Of course, do get in touch if you need help with updating.
Contact us via your Customer Centre and Support Site: https://support.wiiisdom.com/
The Pipelines section now offers a single, unified list view that combines owned and shared pipelines into one menu. This new interface replaces the previous dual-view (card and list) design and provides quick access to essential information and actions.
This improvement simplifies navigation, reduces confusion, and makes pipeline management more efficient. Users can now view all pipelines in one place, understand their status at a glance, and perform key actions without switching views.
Pipelines created or updated via the Public API can now include the Row Count step, previously only available through the user interface.
This enhancement ensures that all pipeline steps offered in the designer are now accessible programmatically.
This update enables full automation of pipeline creation and integration with Path-to-Production workflows, eliminating manual intervention and improving efficiency for enterprise environments. It supports both Power BI and Tableau reports, making it easier for BI teams to maintain consistency and scalability across platforms.
A new Report Policy Enforcement step is now available for pipelines in Wiiisdom Cloud Platform. This step automatically evaluates selected Power BI reports against predefined performance and usability rules before promotion to production. A new test category, BI Assert Policies, has been added to enhance validation capabilities. This step is also configurable via the API.
Administrators can configure the priority of each rule within the BI Assert Policies section in Admin Mode.
It introduces a configurable scoring system to enforce quality standards.
This feature reduces manual checks, improves consistency, and ensures that only reports meeting enterprise performance and usability requirements are promoted. It helps organizations maintain governance, reliability, and trust in their BI content.
A new validation step is introduced for pipelines in Wiiisdom Cloud Platform to detect unexpected changes in DAX query results over time. This feature compares query outputs at two points in time and flags anomalies based on configurable rules such as Result must be different or Result must be the same
For example, you can now copy the DAX query generated by the Performance Analyzer and leverage this validation step to monitor its results over time. This ensures that even complex, custom queries remain consistent and reliable as data evolves.
This enhancement provides proactive monitoring of semantic-level data integrity, helping organizations catch silent anomalies before they impact executive dashboards or decision-making. It reduces reliance on manual checks and post-incident investigations, ensuring greater trust in analytics.
The manual BI platform creation form for Power BI has been redesigned to improve clarity and align with Azure terminology.
The fields have been reordered so that Tenant ID now appears after Client ID, and the labels have been updated to match Azure naming conventions: Application (client) ID, Directory (tenant) ID, and Secret value.
Each field now includes a tooltip with helpful descriptions and a “Learn more” link to the WCP First Steps documentation.
These changes make the configuration process easier to understand, reduce confusion during setup, and ensure consistency with Azure standards, resulting in a smoother onboarding experience.
You can now include an Open Workbook step in pipelines created or updated via the Public API. This step supports selecting workbooks and setting an optional duration limit for loading.
This enhancement enables automated performance checks in Path-to-Production workflows, helping teams validate workbook readiness and ensure smooth, high-quality deployments.
▪ Scheduled runs skipped due to pipeline disablement now display as “Expired” for clearer tracking and filtering.
▪ Open Workbook step is finishing in Technical Error when all Workbooks were opened correctly (Impact: High)
Description: In specific conditions, a pipeline can finish in a Technical Error state even if all Workbooks were opened correctly.
ID: WOFT-3120
▪ Open Workbook with 150+ views may result in error (Impact: Medium)
Description: When setting more than 150 workbooks in the “Open Workbook” step, the pipeline ends in an “Error” step.
ID: WOFT-3071
▪ Step execution start date displayed only while pipeline is running (Impact: Medium)
Description: Execution start date is missing in a finished pipeline report.
ID: WOFT-3029
▪ No Predictive Scoring data for a BI Platform that was properly configured (Impact: Medium)
Description: No Predictive Scoring data for a BI Platform that was properly configured.
ID: WIIIS-2157
▪ Some Semantic Models are missing from the daily refresh compute insight when the last 7 days scope is selected, and the daily average compute value is incorrect (Impact: Medium)
Description: Not all Semantic Models in a Power BI tenant are listed in the daily refresh compute insight of the Predictive Scoring feature when the “Last 7 Days” scope is used” and the average daily refresh compute value displayed in incorrect.
ID: WIIIS-2138
▪ Error trying to run a Step that contains a DAX query with ORDER BY (Impact: Medium)
Description: Running a PowerBI Pipeline Step configured in DAX mode fails when the DAX query contains an “ORDER BY” clause.
ID: WIIIS-2002
▪ Cannot create a pipeline if a workspace does not contain any report (Impact: Medium)
Description: If your workspace only contains only semantic models, the designer will prevent you from saving the pipeline due to “invalid configuration” in certification post process. The workaround is to select a second workspace without any other change.
ID: WIIIS-1990
▪ Certification is propagated to deployed content (Impact: Medium)
Description: When you use the Deploy Content step to deploy a report that has previously been certified, the deployed artifact is now also certified. Any change in the source certification is propagated to the deployed report.
ID: WIIIS-1783
▪ A pipeline in "PREPARING" status can still be launched (Impact: Medium)
Description: If your pipeline is in “Preparing” status because some baselines are being processed you can still launch it, resulting in inconsistent results.
ID: WIIIS-1359
▪ Some capacities are not listed when configuring Predictive Scoring for a BI Platform (Impact: Medium)
Description: Some capacities are not listed when configuring the Predictive Scoring with capacity monitoring feature on Power BI manual BI platforms.
ID: WIIIS-2125
▪ Day of week does not appear fully in scheduling recurring modal (Impact: Low)
Description: In the recurring scheduling modal, the full name of the selected weekday is not displayed correctly. This issue impacts user experience by creating ambiguity when setting up recurring events, as users cannot clearly identify the chosen day. Ensuring the full weekday name is visible is critical for accurate scheduling and preventing misconfigurations.
ID: WOFT-3068
▪ Header values in the WebRequest PPA are blocked to 50 characters (Impact: Low)
Description: You cannot configure Web Request Post Process Action if your header name or value is more than 50 chars long.
ID: WOFT-3056
▪ Allow pipeline ownership transfer and sharing only to users with the Pipeline Architect role (Impact: Low)
Description: You can make a user who is not a pipeline architect the owner of your pipeline even if this user is not allowed to design or run pipeline.
ID: WOFT-3055
▪ Predictive Scoring logs were polluted by a NPE exception (Impact: Low)
Description: Predictive Scoring Extractor pollutes the logs with an unattended exception.
ID: WOFT-3041
▪ Unable to schedule a pipeline when the browser timezone is not recognized (Impact: Low)
Description: A user with a timezone not recognized cannot schedule a recurring pipeline.
ID: WOFT-3014
▪ We can list more than 100 audit events at a time (Impact: Low)
Description: In some page where our tables are paginated, we can tweak the HTTP request to have more than 100 elements, leading to server resource exhaustion.
ID: WIIIS-2161
▪ Large number use scientific notation in DAX Result Variation execution report (Impact: Low)
Description: When the result of your DAX query is a large number we display it in scientific notation (e.g 4.2E9) instead of normal notation (4,200,000,000)
ID: WIIIS-2137
▪ The name of the new pipeline created from Predictive Scoring is not unique (Impact: Low)
Description: When creating a Continuous Certification pipeline directly from the Predictive Scoring interface, the default name is not generated to be unique, and as a result, you will face a validation error on save. You just have to manually change the name to be able to save your pipeline.
ID: WIIIS-2086
▪ TVM audit data sort is not correct when downloading the excel file (Impact: Low)
Description: The Excel file generated for the TVM audit data was not sorted correctly, displaying the oldest data first.
ID: WOFT-2948
▪ If database gets shut down while we are processing a long step, the next execution slot is not freed (Impact: Low)
Description: In some specific cases when database becomes unavailable for a short amount of time we may not free an execution slot. Subsequent executions are delayed but not lost.
ID: WIIIS-2115
