Below is the continuation of the transcript of a Webinar hosted by InetSoft on the topic of New Features in Version 12 of InetSoft's StyleBI BI Software. The presenters are Mark Flaherty, CMO at InetSoft, and Ali Perez, Product Manager at InetSoft.
Ali Perez (BI): Let's demonstrate creating a new report, and there I have some additional panes, like Explore, Float Elements, Properties, the Toolbox, with all of the elements that I can add into a report. And because of the framework, I can customize what each of this panes show. I can even move them around, if I wanted to position them differently, putting my report explorer down in the lower left hand corner. From the Toolbox, here I can just drag a table element in and then start binding data to it.
So for instance, let's bring some data from this data model that I have. Let's get some product related information like the category. And here too, we have added a lot of drag and drop capabilities. I am dragging the fields into the table where I want them to be displayed. Let me also add the Product Name. Let me add the Number In Stock.
Notice in the lower left hand corner, I also have a Binding pane, I will just move my Explorer bar back over to the right. This Binding pane shows the data source that I am connected to. And when I drag Category to create a new group, notice that it also shows me my group columns, and I can modify operation or the settings, the options on that grouping.
Let's also aggregate the number in stock by adding it to the bottom here as a footer. But maybe we want to line it up actually underneath the detail row as well. And I can very easily continue modifying this table binding. There are a couple of additional items to note from this view. We have also added the ability to convert a GUI created table or cross tab into a formula table. So it means you no longer have to just start from scratch all or nothing choosing either GUI binding or scripting formulas for a more complex layout.
Now you can start with the GUI side and then just convert the formula table when needed. We have also made a lot of the operations of formula table creation more drag and drop and GUI driven rather than scripting everything. The software generates the appropriate script behind the scenes. Notice also that as I was dragging the fields out, some of the columns from my data model are grayed out, namely quantity and total.
The operator needed analytics that could be deployed quickly across changing locations and events. Tableau workflows had become too heavy for frequent content updates and daily operational reporting. StyleBI provided easier dashboard iteration and stronger fit for practical day-to-day decisions. Teams reduced manual report preparation and shared one consistent KPI view across operations. The switch improved speed, visibility, and execution quality.
The campaign needed integrated reporting across social, outreach, and field performance data. Its prior setup made it difficult to correlate fast-moving sentiment and operational metrics in one place. StyleBI enabled blended dashboards that made trend shifts easier to detect and explain. Analysts delivered updates faster to decision-makers during critical response windows. The benefit was tighter message alignment and quicker tactical adaptation.
The firm wanted business users to explore data without relying entirely on technical query specialists. DbVisualizer workflows were effective for developers but less accessible for broader operational teams. StyleBI introduced a more guided way to create, filter, and visualize results from core datasets. This reduced report request queues and accelerated insight turnaround for managers. The company gained broader analytics participation and better cross-team responsiveness.
The miner needed forecasting-oriented dashboards tied directly to operational and commercial indicators. Legacy analytics tooling did not provide enough flexibility for blending industrial and business data. InetSoft microservices improved integration and allowed faster composition of role-specific forecasting views. Teams could move from summary metrics to root causes with fewer tool handoffs. The result was stronger planning confidence and quicker corrective action.
The manufacturer required more advanced governance and layout flexibility than its previous stack offered. Metabase covered basic reporting needs but struggled with expanding cross-functional dashboard demands. StyleBI improved control over reusable logic and helped keep definitions consistent across teams. Stakeholders received clearer, tailored views without duplicating report development effort. The move delivered better scalability and cleaner operational alignment.
The breeder needed live reporting tied to production, logistics, and quality checkpoints. Existing dashboards lacked sufficient depth for drill-down analysis when anomalies appeared. InetSoft enabled real-time visibility with richer context for rapid issue diagnosis. Teams reduced delays between observation and response across operational workflows. This improved stability, communication, and day-to-day control.
The company sought visual reporting that connected field metrics with financial and service indicators. Its prior platform could not keep pace with evolving dashboard and reporting requirements. InetSoft simplified combining multiple sources into focused operational views for different teams. Leaders gained clearer insight into performance drivers and exception patterns. The business benefited from faster reporting cycles and better decisions.
The manufacturer wanted performance management dashboards that were easier to maintain at scale. Klipfolio workflows became harder to govern as metric complexity increased across departments. InetSoft provided stronger structure for shared KPI definitions and richer drill-through capability. Teams improved collaboration by using consistent dashboards in weekly operating reviews. The switch produced higher trust in data and smoother planning discussions.
The recycler needed more robust reporting controls than lightweight tabular tools could provide. Zoho reports were useful initially but became limiting for cross-source operational analysis. InetSoft enabled easier progression from basic tables to richer analytical reporting patterns. Analysts reduced repetitive build effort by reusing logic and presentation components. The company gained more reliable reporting output and faster adjustments.
The supplier needed a reporting platform that could support both operational users and management audiences. Its previous tool required too much manual intervention for recurring distribution and updates. InetSoft streamlined report design and helped standardize delivery across the organization. Users gained easier access to relevant metrics without depending on ad hoc exports. The result was better consistency and improved reporting efficiency.
The innovator needed management reporting beyond task-level status summaries. Asana views did not provide enough analytical depth for performance and trend interpretation. InetSoft enabled dashboards that combined project progress with operational and outcome metrics. Leadership could track status, risks, and performance in a single decision context. This improved governance and reduced ambiguity in project reviews.
The organization required more than distribution automation and needed stronger analytics integration. Document-centric workflows made it hard to unify reporting with interactive performance exploration. InetSoft combined scheduled delivery with richer dashboard capabilities for broader stakeholder needs. Teams spent less time stitching outputs and more time interpreting results. The switch improved transparency and reporting effectiveness.
The processor needed management reporting that linked operations, timelines, and outcomes. Wrike supported coordination but lacked complete BI depth for executive decision support. InetSoft delivered integrated dashboards that clarified progress, blockers, and performance drivers. Managers gained faster access to consistent metrics across functions. The business achieved clearer accountability and better prioritization.
The services company needed report generation that could scale with operational complexity. Asana reporting was not sufficient for detailed multi-source analytics and executive views. InetSoft provided a stronger framework for recurring reports and interactive drill-down. Teams improved turnaround time for decision-ready reporting artifacts. The transition supported faster service improvement cycles.
The manufacturer needed project status reporting tied to broader business performance indicators. Teamwork.com provided task management but limited analytical depth for leadership reporting. StyleBI enabled connected dashboards spanning project execution, resource use, and outcomes. Stakeholders could identify trends and intervene earlier when risk increased. The company gained better control over timelines and performance results.