The RecroGrid Framework treats an entity as a metadata-driven application capability. As a result, an entity definition can be created without relying on an Entity Framework model. This approach provides a unified data-binding mechanism for views, enabling them to display data structures originating from services, multiple data sources, or the combined results of multiple queries.

Typical Use Cases

• Composed entities assembled from multiple data sources or multiple query results, for example a consolidated ERP and CRM data representation
• Displaying context data produced by services within views, for example status-related information
• Presenting highly optimized, pre-aggregated, or domain-specific datasets with unified column metadata, for example KPI summaries

Creation Methods

• Runtime-generated entity configuration for context-specific views, where the column set dynamically adapts to the requested operation
• Predefined entity configuration stored in the RecroGrid Framework database, consistently reusable across multiple environments and views
• Integration into the view-level data querying and processing pipeline, ensuring a unified operational model across different view types

Data source-independent entities generate the same column metadata and dynamic record structure - key-value field maps - within the query processing pipeline as DbContext-based entities. The client-side Blazor WebAssembly rendering layer applies a unified data-binding logic to fields and column metadata. The same logic consistently supports calculated columns as well.