Official way to query Stage Databases in ODC beyond Development
116
Views
3
Comments
New
Database

In ODC it would be extremely valuable to have an official and supported way to perform direct queries against application databases in stages beyond Development.

Currently, the only practical way to inspect database data is via ODC Studio in Development stage. Once the application is promoted to QA / Pre-Prod / Production, there is no official mechanism to query the database, even for simple troubleshooting or validation scenarios.

This creates a real operational gap:

In many cases, a simple SELECT query would immediately explain an issue. Instead, developers are forced to add temporary logging, deploy heavy diagnostic logic or reproduce issues back in Development (not always possible or effective).

Adding logs purely for troubleshooting, increases noise in the code (lots of LogMessages) and often feels wrong when a safe DB query would solve the issue in minutes

What would help:

An official DB query tool for ODC Studio or ODC Portal feature for controlled data inspection with proper auditing, permissions, and safeguards.

Why this is important:

  1. Modern cloud-native platforms rely heavily on observability and controlled introspection
  2. Troubleshooting issues in higher environments without DB visibility is unnecessarily hard
  3. This would significantly improve developer experience, support efficiency, and confidence in ODC

Having an official, supported way to query stage databases in ODC would remove the need for workarounds and align ODC with real-world operational needs.

Until there is an official tool or functionality from OutSystems, you could use the following Forge component, which does exactly what you're looking for.

https://www.outsystems.com/forge/component-overview/22538/database-access-odc

Hi Remco,

Thanks for the link. I’m aware of community tools like this Forge component. However, this kind of functionality really needs to be provided as an official OutSystems tool, so companies can use it with confidence in production. Community components can be useful, but they don’t replace an officially supported solution.

Could OutSystems not validate and adopt the existing database forge component?