<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Quick BI</title>
    <description>The latest articles on DEV Community by Quick BI (@quick_bi_lydaas).</description>
    <link>https://dev.to/quick_bi_lydaas</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3852979%2Fad819f79-d276-405c-8f6f-b61f98912fdc.png</url>
      <title>DEV Community: Quick BI</title>
      <link>https://dev.to/quick_bi_lydaas</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/quick_bi_lydaas"/>
    <language>en</language>
    <item>
      <title>测试</title>
      <dc:creator>Quick BI</dc:creator>
      <pubDate>Wed, 08 Jul 2026 02:16:02 +0000</pubDate>
      <link>https://dev.to/quick_bi_lydaas/ce-shi-17ae</link>
      <guid>https://dev.to/quick_bi_lydaas/ce-shi-17ae</guid>
      <description>&lt;p&gt;测试&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Beyond Dashboards: How a Dual-Engine Approach Solves the Hardest Data Reporting Problems</title>
      <dc:creator>Quick BI</dc:creator>
      <pubDate>Fri, 05 Jun 2026 02:39:39 +0000</pubDate>
      <link>https://dev.to/quick_bi_lydaas/beyond-dashboards-how-a-dual-engine-approach-solves-the-hardest-data-reporting-problems-1pkd</link>
      <guid>https://dev.to/quick_bi_lydaas/beyond-dashboards-how-a-dual-engine-approach-solves-the-hardest-data-reporting-problems-1pkd</guid>
      <description>&lt;p&gt;Every data team eventually hits the same wall. You spend days building a complex financial reconciliation report inside a BI dashboard—only to watch it break under nested headers, cross-sheet references, and multi-level grouping. So what happens next? Someone opens Excel. Again.&lt;/p&gt;

&lt;p&gt;And then there's the other side: a high-stakes executive presentation where a wall of charts says everything and nothing at the same time. The question from the room is always the same: &lt;em&gt;"What's the story here?"&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;These aren't competence problems. They're tool-mismatch problems. A single dashboard can't serve both the CFO's month-end close and the CEO's strategic review. That's why we built a &lt;strong&gt;dual-engine approach&lt;/strong&gt; in &lt;a href="https://quickbi.aliyun.com" rel="noopener noreferrer"&gt;Lingyang Quick BI&lt;/a&gt;: &lt;strong&gt;Spreadsheets&lt;/strong&gt; for precision, and &lt;strong&gt;Data Screens&lt;/strong&gt; for storytelling.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fhe6f3xblkj6xbqmiuby7.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fhe6f3xblkj6xbqmiuby7.png" alt="Quick BI dual engine architecture" width="799" height="265"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The Spreadsheet Engine: Built for Finance and Power Analysts
&lt;/h2&gt;

&lt;p&gt;When we talk about "spreadsheets" in a BI context, most people assume we mean a basic grid with a database connection. That's not what this is.&lt;/p&gt;

&lt;p&gt;Quick BI Spreadsheets were designed around a simple observation: &lt;strong&gt;don't fight user habits—augment them&lt;/strong&gt;. Financial analysts and supply chain operators already know Excel fluently. The friction comes when those locally built sheets become siloed, version-drifted, and manually refreshed.&lt;/p&gt;

&lt;p&gt;Here's what changes when you move that workflow into Quick BI Spreadsheets:&lt;/p&gt;

&lt;h3&gt;
  
  
  400+ Native Excel Functions, Zero Re-Learning
&lt;/h3&gt;

&lt;p&gt;The spreadsheet engine supports nearly 400 high-frequency Excel functions natively. Cross-sheet references, array formulas, VLOOKUP equivalents—all familiar syntax. A seasoned analyst can start building on day one without a training course.&lt;/p&gt;

&lt;h3&gt;
  
  
  Cell-Level Precision for Complex Report Structures
&lt;/h3&gt;

&lt;p&gt;We engineered the component to handle the kinds of reports that make traditional BI tools choke:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Multi-level and merged headers&lt;/li&gt;
&lt;li&gt;Multi-level floating elements and grouping&lt;/li&gt;
&lt;li&gt;Diagonal headers&lt;/li&gt;
&lt;li&gt;Multiple report bodies on a single sheet&lt;/li&gt;
&lt;li&gt;Business detail lists, grouped reports, cross-tab reports, master-detail reports, multi-column layouts, query-style reports, and data entry forms&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Real-Time Database Connectivity
&lt;/h3&gt;

&lt;p&gt;This is where the spreadsheet stops being "just Excel." Reports bind directly to underlying data sources. When a transaction posts in the ERP, the spreadsheet reflects it—no manual refresh, no "is this the latest version?" email chains.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fdnr6ni8igw4l8spmc1ef.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fdnr6ni8igw4l8spmc1ef.png" alt="Quick BI Spreadsheets interface" width="800" height="447"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The Data Screen Engine: Executive-Grade Visual Storytelling
&lt;/h2&gt;

&lt;p&gt;Now flip to the other problem. A dashboard full of charts is not the same as a data narrative. Executives don't want to explore data—they want to &lt;em&gt;see the point&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;Quick BI Data Screens address this by treating visualization as &lt;strong&gt;presentation design&lt;/strong&gt;, not just data rendering.&lt;/p&gt;

&lt;h3&gt;
  
  
  Cinematic-Quality Components, Zero Code
&lt;/h3&gt;

&lt;p&gt;The component library ships with industry-specific templates and assets that you can install with one click. Charts now support animation effects to reinforce the visual atmosphere. The result: something that looks like it came from a professional design agency, built by a business user in an afternoon.&lt;/p&gt;

&lt;h3&gt;
  
  
  Narrative-Driven Presentation
&lt;/h3&gt;

&lt;p&gt;The data screen engine supports &lt;strong&gt;multi-scene, multi-page storyboarding&lt;/strong&gt;. Instead of dumping every metric onto one page, you sequence them:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Where we are&lt;/strong&gt; — current state&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What moved&lt;/strong&gt; — key drivers&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Where we're going&lt;/strong&gt; — forward view&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fshtgdylbo0b8nlwhrc3d.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fshtgdylbo0b8nlwhrc3d.png" alt="Quick BI Data Screen example" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This is "point of view first" visualization. You lead with the conclusion, then let the data back it up.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Both Engines Matter
&lt;/h2&gt;

&lt;p&gt;The underlying principle is straightforward: &lt;strong&gt;the right tool for the right job&lt;/strong&gt;.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Concern&lt;/th&gt;
&lt;th&gt;Spreadsheets Handle&lt;/th&gt;
&lt;th&gt;Data Screens Handle&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Primary audience&lt;/td&gt;
&lt;td&gt;Finance, analysts, operators&lt;/td&gt;
&lt;td&gt;Executives, leadership, board&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Data complexity&lt;/td&gt;
&lt;td&gt;Multi-level headers, cross-sheet logic, custom formulas&lt;/td&gt;
&lt;td&gt;Aggregated KPIs, visual narrative, brand-level polish&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Update frequency&lt;/td&gt;
&lt;td&gt;Real-time, automated refresh&lt;/td&gt;
&lt;td&gt;Periodic, event-driven (reviews, summits, command centers)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Output&lt;/td&gt;
&lt;td&gt;Pixel-accurate compliance reports&lt;/td&gt;
&lt;td&gt;Immersive, story-driven presentations&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Putting them together creates an end-to-end flow: fine-grained processing → macro-level visualization. The data doesn't get rewritten between the two engines; it just gets presented differently.&lt;/p&gt;

&lt;h2&gt;
  
  
  What This Means in Practice
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Month-end close&lt;/strong&gt;: Finance builds complex reconciliation reports with multi-level grouping and cross-tab logic—no manual VLOOKUP chains, no version drift.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Annual strategy meeting&lt;/strong&gt;: The same underlying data powers a cinematic data screen that walks the leadership team through the year's narrative in three acts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Supply chain monitoring&lt;/strong&gt;: Operational teams track granular metrics in spreadsheets; directors review summary dashboards on screens in the command center.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The data is consistent. The presentations are context-appropriate. Nobody's manually copy-pasting between tools.&lt;/p&gt;

&lt;h2&gt;
  
  
  Get Started
&lt;/h2&gt;

&lt;p&gt;If you've been forcing a single dashboard to do jobs it was never designed for, it's worth trying a dual-engine approach. Quick BI Spreadsheets and Data Screens are available now.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://quickbi.aliyun.com" rel="noopener noreferrer"&gt;Try Quick BI →&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Have questions about migrating your existing Excel-based reports into a live BI environment? Drop a comment below—I'd love to hear what your toughest reporting challenge is.&lt;/p&gt;

</description>
      <category>analytics</category>
      <category>businessintelligence</category>
      <category>dataviz</category>
      <category>quickbi</category>
    </item>
    <item>
      <title>Testing the dev.to API: long-form article with images 🚀</title>
      <dc:creator>Quick BI</dc:creator>
      <pubDate>Fri, 05 Jun 2026 01:51:10 +0000</pubDate>
      <link>https://dev.to/quick_bi_lydaas/testing-the-devto-api-long-form-article-with-images-m0d</link>
      <guid>https://dev.to/quick_bi_lydaas/testing-the-devto-api-long-form-article-with-images-m0d</guid>
      <description>&lt;p&gt;This article was published programmatically through the &lt;strong&gt;dev.to Articles API&lt;/strong&gt;&lt;br&gt;
to verify that long-form content with images works end-to-end.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why dev.to is the easy one
&lt;/h2&gt;

&lt;p&gt;Unlike LinkedIn, X, or Instagram, dev.to needs nothing more than a single API&lt;br&gt;
key in a header — no OAuth, no cost.&lt;/p&gt;

&lt;h2&gt;
  
  
  Inline image
&lt;/h2&gt;

&lt;p&gt;Images are referenced by public URL, right inside the Markdown body:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F5aygxi67vae56eujcegl.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F5aygxi67vae56eujcegl.png" alt="sample image" width="800" height="511"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Code blocks work too
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="nf"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;hello from the dev.to API&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That's it — title, Markdown body, a cover image, and a couple of inline images.&lt;/p&gt;

</description>
      <category>api</category>
      <category>automation</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
