In this blog post I will show you how to put the facets in a Apex facet search in a drawer to make more room for the search result. This feature also came from a customer requirement. The wish to see most or all of the columns on the screen without the need for horizontal scroll. A standard facet search page showing my Strava data. The facets region take up some part of the screen all the time. When choosing a facet you want more space for columns in the report.

A customer using a facet search page complained about the horizontal scrollbar being at the bottom of the page when seeing a lot of data. First you have to scroll down, maybe hundreds of rows before you can scroll to the right.

At work I was tasked with an apex application using very long time from logon to the front page was shown. This time went up significantly moving from on prem to OCI. The apex app is integrated with Oracle E-business suite and authenticate using OEBS. For me the logon time was 24 seconds. For one user with more organizational access, the logon time was 1 minute 19 seconds. After some rudimentary logging I find that authentication is very fast. "On page load" logging for the front page is just a few millisecond after authentication process finished.

This is a three part series. It is about using Apex for integration work. It was presented at Oracle User Group Norway (OUGN) on the 15.05.25. The first part focused on creating your own REST service. The service retrieved data from a third party and stored it in Apex. The second part detailed how to use Oracle ERP integration service to upload data. We uploaded currency data to ERP. This part will be about how to use Apex Workflow to orchestrate the integration. Why Workflow? In earlier projects before workflow I have orchestrated similar tasks with a lot of database jobs.

This is a three part series. It is about using Apex for integration work. It was presented at Oracle User Group Norway (OUGN) on the 15.05.25. The first part focused on creating your own REST service. The service retrieved data from a third party and stored it in Apex. This part will detail how to use Oracle ERP integration service to upload data. In this example we will upload currency data to ERP. The third part will be about how to use Oracle Workflow to orchestrate the integration. ERP Integration Service is a huge rest service in Oracle ERP.

This is a three part series. It is about using Apex for integration work. It was presented at Oracle User Group Norway (OUGN) on the 15.05.25. The first part focuses on creating your own REST service. This service retrieves data from a third party and stores it in Apex. Later, we will relay it to Oracle ERP. The Second part will detail how to use Oracle ERP integration service to upload data. In this example we will upload currency data to ERP. The third part will be about how to use Oracle Workflow to orchestrate the integration.

Denne helgen har jeg gjennomført en spennende migrering fra en on-prem Oracle APEX-installasjon til Oracle Cloud Infrastructure (OCI). Dette prosjektet har vært en reise fra min forrige jobb. Der jobbet jeg i markedsavdelingen og ble først gang introdusert for APEX. Det startet med å samle kundedata og bygge et CRM-system, som raskt ble et viktig verktøy både for markeds- og produktavdelingen. Kunde- og produktdataene lå opprinnelig i noen Excel-ark. Basert på disse bygget jeg den første versjonen av CRM-systemet i en lokal APEX Free-instans. Min bakgrunn som konsulent, med bred erfaring i PL/SQL fra konsulentavdelingen i selskapet, ga et godt utgangspunkt for å lære APEX og utvikle denne løsningen.

Deploying an Apex application involves installing all the database objects it relays on to work. Wetter it is a new install or an upgrade you want the Supporting Objects to run without flaws. Oracle 23ai makes this task somewhat easier. In this blog post I will give focus to tables and seed data. Other objects are fairly easy. But first some short notes on the easy one's: Views support create or replace and are only dependent on underlying tables to be installed firstly. Sequences support the new exist clause. So an sequence can be created like below.

This blog post guides users on setting up Apex for email sending via Oracle Cloud Infrastructure (OCI). It details user creation, group and policy formation, and SMTP credential generation. The process concludes with configuring APEX for email, testing email delivery, and troubleshooting any issues that may arise during the setup.

In a project I'm working on we have to access APEX Developer from a Citrix Client. Until recently I used Postman for testing my own REST services in that project and also ERP Rest Services. We are closing in on finalizing this project and security is tighten a few more steps. Can not use Postman web anymore. We need to test our APEX REST services in some way. That leaves us with: Buying enterprise license of Postman to install on Citrix (Required on Citrix environments) Use Soap UI that have support for REST…

Creating Apex Schema/User and Workspace can be done in two ways. The right way and the "wrong" way. The "wrong" way is not entirely wrong. Yet, you waive some of your control over schema name and initial grants. I will show both ways, but I recommend method two. I will also walk you through different grants and what they do. Method one: Create Schema using Apex Administration Services

Language can be trouble in API integration with Fusion. In Norway we have special letters Æ,Ø, Å which is not in the English alphabet. Name of Counties are written differently than in English. Italia = Italy, Tyskland=Germany, etc. When developing a Supplier Integration in APEX, I used my own user as a Integration user. I prefer using American English in my setup. If googling something all menu options and solutions uses American English, so much easier to find stuff when using English. My Language setup for my ERP user. As the projects goes along, logon to ERP is changed to Azure logon.

Oracle Cloud Infrastructure (OCI) buckets are designed for quick and secure storage of unstructured data. A bucket can holds objects, like files, images, backups, or any data in its original form. Buckets can be private and only accessible to authorized users. They can also be public for sharing resources like static website content or downloadable files. Files can be downloaded in a web browser using pre authenticated url's. I use buckets when I run BI reports from Apex and store big payloads from the reports in buckets. Files can be handed to data warehouse or be read into apex table for preparation for data warehouse.

It's only Elvis and CSV who can speak the headline with confidence. In a project I'm working on, another developer reported an issue. A report I made to get related segment values from ERP to Apex was failing. Strange, It has worked for a long time, getting segment values and related segment values on a scheduled basis. Pressing the manual "Refresh" button returns the error. The code block below shows the bad log and how the same line looks in the BI report. Between the 0,,Y the segment name "Unspecified" is missing.

In this blog post, we explore OAuth2 authentication further. It builds on the earlier blog post: Secure your Oracle APEX REST-service with OAuth2 – Standal.blog If we where to call the REST service, implemented earlier, we can go about it this way. First we will create a Web Credential inside APEX Builder to keep the client id and secret secure. In App builder, choose "Workspace Utilities", then click on "Web Credentials" and "Create". Here the credential is created as OAuth2 Client Credentials. The use of the credentials is limited to the apex.oracle.com domain and the token routine.