View Issue Details

IDProjectCategoryView StatusLast Update
0000046Inlyra StudioInput Toolspublic2026-09-27 20:37
Reporterinlyradev Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Summary0000046: Add Stored Procedure support to Database Input
DescriptionGoal:
Allow Inlyra Studio Pro users to execute database stored procedures that return tabular results and use those results as normal workflow input.

Phase 1 scope
Add a new Stored Procedure mode to Database Input alongside the existing table/view and custom query options.
Example:
Source Type

( ) Table / View
( ) Custom Query
(•) Stored Procedure

When Stored Procedure is selected:
1. Use the selected saved database connection.
2. Discover available stored procedures for that connection/provider.
3. Let the user choose a procedure from a dropdown.
4. Discover the procedure’s input parameters where supported.
5. Display the parameters in a simple grid.
6. Let the user enter literal/static values for each parameter.
7. Validate/cast those values to the parameter’s database type.
8. Execute the procedure.
9. Use the first returned tabular result set as the Database Input output.
Proposed UI
Stored Procedure
[ dbo.GetDailyMarks ▼ ]

Parameters

Parameter Type Value
@BusinessDate Date 2026-09-27
@Desk String ERCOT
@IncludeInactive Boolean false

[ Discover Schema ] [ Preview (100 rows) ]

Phase 1 parameter behavior
Parameter values are configured directly in the tool and remain static until the workflow is edited.
Examples:
@BusinessDate = 2026-09-27
@Desk = ERCOT
@IncludeInactive = false

Dynamic expressions and workflow/system variables are not part of phase 1.
Result-set behavior
For the initial implementation:
- support procedures that return a tabular result set
- use only the first result set
- procedures returning no tabular result should produce a clear configuration/execution message
- multiple result sets are out of scope initially
- output parameters and procedure return values are out of scope initially
This keeps the feature compatible with Inlyra’s existing single-table node output model.
Schema discovery
Stored procedures may require parameter values before their output schema can be determined.
Discover Schema / Preview should therefore execute the procedure using the configured parameter values.
Because stored procedures can contain side effects, the UI/help should clearly state that schema discovery and preview may execute the procedure.
For phase 1, documentation should recommend using Stored Procedure Input with procedures intended for data retrieval/read-only use.
Provider rollout
Recommended first provider:
Microsoft SQL Server
SQL Server has straightforward stored-procedure execution and parameter support through ADO.NET.
After the interaction model is proven, support can be evaluated for:
- PostgreSQL
- MySQL
- MariaDB
- Oracle
Provider behavior should remain isolated behind the database-provider abstraction because procedure discovery and execution differ across database systems.
Future phases
Later enhancements could add dynamic parameter values such as:
@BusinessDate = Sys.Today()
@WorkflowName = Sys.GetWorkflowName()

and user/workflow variables such as:
@Region = Var.Region

Possible future capabilities:
- system/runtime variable namespace
- workflow-defined variables
- Server-supplied parameters
- formula/expression-based parameter values
- output parameters
- multiple result sets
- procedure/action execution without tabular output
TagsNo tags attached.
Report TypeFeature Request
EditionBoth
Operating SystemWindows 11

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2026-09-27 20:37 inlyradev New Issue