<?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: Faraz Ahmed</title>
    <description>The latest articles on DEV Community by Faraz Ahmed (@farazz5).</description>
    <link>https://dev.to/farazz5</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3710834%2Fd03bd366-9410-45fd-887f-06efb4c3920b.png</url>
      <title>DEV Community: Faraz Ahmed</title>
      <link>https://dev.to/farazz5</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/farazz5"/>
    <language>en</language>
    <item>
      <title>How I finally simplified nested JSON reporting in Oracle APEX 24.2</title>
      <dc:creator>Faraz Ahmed</dc:creator>
      <pubDate>Wed, 11 Mar 2026 07:51:17 +0000</pubDate>
      <link>https://dev.to/farazz5/how-i-finally-simplified-nested-json-reporting-in-oracle-apex-242-3fm2</link>
      <guid>https://dev.to/farazz5/how-i-finally-simplified-nested-json-reporting-in-oracle-apex-242-3fm2</guid>
      <description>&lt;p&gt;Anyone else feel like they spend 80% of their reporting time just flattening JSON?&lt;/p&gt;

&lt;p&gt;I recently upgraded a project to APEX 24.2, and while the native data export is great for simple tables, I hit a wall with a client who needed heavily branded, multi-level reports. I was staring at a massive PL/SQL package just to handle the data mapping when I decided to try a different approach.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Problem&lt;/strong&gt;&lt;br&gt;
Mapping nested JSON to a specific layout usually means:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Writing complex SQL/JSON logic.&lt;/li&gt;
&lt;li&gt;Manually defining every single column and header.&lt;/li&gt;
&lt;li&gt;Redoing half the work if the layout changes by two pixels.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;The "Low-Code" Fix&lt;/strong&gt;&lt;br&gt;
Instead of coding the mapping, I used the &lt;a href="https://maxprint.io/" rel="noopener noreferrer"&gt;MaxPrint&lt;/a&gt; designer. Here’s the quick workflow I used:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Grab the JSON: I pulled a sample of my nested data directly from the APEX SQL Workshop.&lt;/li&gt;
&lt;li&gt;Visual Mapping: I pasted that JSON into the designer. It automatically recognized the structure, so I just dragged the fields onto the report canvas. No code required for the binding.&lt;/li&gt;
&lt;li&gt;The Integration: I used the MaxPrint plug-in to trigger the report from a button in my APEX app.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;The Result&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I managed to cut down the "data-to-layout" phase from a full afternoon to about 20 minutes. The best part? When the client asked to move a logo or change a font, I just did it in the visual editor without touching a single line of PL/SQL.&lt;/p&gt;

&lt;p&gt;Has anyone else moved away from manual template coding in 24.2? I'm curious if there are other tools out there that handle the JSON mapping this smoothly.&lt;/p&gt;

</description>
      <category>oracleapex</category>
      <category>lowcode</category>
      <category>sql</category>
      <category>javascript</category>
    </item>
    <item>
      <title>Any Recommendation for a modern Oracle APEX reporting tool?</title>
      <dc:creator>Faraz Ahmed</dc:creator>
      <pubDate>Thu, 05 Mar 2026 07:33:03 +0000</pubDate>
      <link>https://dev.to/farazz5/any-recommendation-for-a-modern-oracle-apex-reporting-tool-1ki3</link>
      <guid>https://dev.to/farazz5/any-recommendation-for-a-modern-oracle-apex-reporting-tool-1ki3</guid>
      <description>&lt;p&gt;I want to generate branded PDF invoices and Excel statements in APEX 24.2. The native APEX_DATA_EXPORT is too limited for these custom layouts. Does anyone have a recommendation for a low-code tool that is easy to integrate?&lt;/p&gt;

</description>
      <category>oracleapex</category>
      <category>lowcode</category>
      <category>database</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
