Recently I have developed an internal application for knowledge sharing using Oracle APEX. In this application, I have used many interesting new features from 19.2 and 20.1.

One of them is the Markdown column. I used Markdown editor items in the form page to use the normal shorthand syntax to format text and code. To display this data, I used the classic report. In classic report, I selected a specific column type as the Markdown, see Figure 1.

Using the classic report with standard template, as shown in Figure 2, the expected result (Figure 3) is obtained. So far, everything is fine.

In our internal application, I want to display the result in non-standard template types, for example, ‘Search Results’ or ‘Value Attribute Pairs – Column’ template. For this purpose, I have changed the template type. But I did not get the result as expected, see Figure 4.1 and 4.2.

4.1: Search Results template

4.2: Value Attribute Pairs – Column template

One possible scenario could be a rendering problem for non-standard templates of the classic report for Markdownified text.

To solve this problem, I have added a dynamic action, shown in Figure 5.1 and 5.2, to refresh the classic report region when the page loads.

5.1: Dynamic action

5.2: Dynamic action

Then it worked as expected, see Figure 6.1 and 6.2.

6.1: Search Results template after adding dynamic action

6.2: Value Attribute Pairs – Column template after adding dynamic action


After discovering this behavior, we discussed it with #orclapex Team. It is registered as Bug now and it will be fixed with the next release.

Maybe there are other workarounds to solve this issue. As of now, I have used this simple approach as a low or no code ? solution.


Keine Kommentare

Kommentar schreiben

* Diese Felder sind erforderlich

Ähnliche Beiträge