Additions

customer_orderline_202501

This release introduces a new version of customer.orderline, evolving from the current beta version. The latest update incorporates a fully JSON-managed field structure, enhancing flexibility, data integrity, and future scalability.

Key Changes & Enhancements

Fully JSON-Managed Fields:
- All relevant attributes of customer.orderline are now structured using JSON formatting.
- Supports dynamic and nested structures for better adaptability to evolving business needs.
Streamlined Data Structure:
- Reduces column proliferation by consolidating attributes within JSON objects.
- Enables more efficient storage and retrieval, particularly for variable and optional fields.
Improved Query Performance:
- Optimised for modern analytics tools that support direct JSON parsing.
- Leverages SQL-native JSON functions for simplified extraction and transformation.
Future-Proof Design:
- Allows for easier schema evolution without disrupting existing integrations.
- Supports extended attributes without requiring database schema modifications.

Impact on Data Consumers

Queries referencing individual fields within customer.orderline may require updates to extract JSON elements explicitly.
JSON processing functions (e.g., JSON_VALUE, JSON_QUERY) should be used for filtering and transformation.
Data pipelines that ingest or process customer.orderline should be reviewed for compatibility.

Alterations

project_details_plus_CAD

This update continues the ongoing improvements to mapping accuracy and data consistency within project_details_plus_CAD. The key focus of this release is enhancing programme descriptions by aligning them with the Framework Name, improving clarity and usability across reporting and analysis.

Next Steps

Support & Feedback: If you encounter issues or require adjustments, please reach out via the Data Engineering team.
Testing & Validation: We encourage users to test queries against the updated structure in beta before full deployment.
Documentation Update: A revised schema reference and example queries are available in the [Knowledge Base / Data Catalogue].

Notes

1. ⚠️ DIFFERENT: customer_orderline.sql
2. 🔴 MISSING IN PRD CONTAINER: customer_orderline_202501.sql
3. ⚠️ DIFFERENT: project_cost.sql
4. ⚠️ DIFFERENT: project_details.sql
5. ⚠️ DIFFERENT: project_details_plus_CAD.sql

Total number of different files: 4
Total number of missing files in DEV CONTAINER: 0
Total number of missing files in PRD CONTAINER: 1

Release 55