Release 86.131

by

1. Core View Corrections – Collation Fix

Files affected

  • busopp_core_details.sql
  • invoice_core_details.sql
  • invoice_meta_codes.sql
  • order_core_details.sql
  • project_core_details.sql

Change

  • Corrected collation on OBJECT_NAME to Latin1_General.

Reason

  • Removes corrupted mojibake characters caused by inconsistent free text handling.

Impact

  • Improves text integrity and consistency across domains.
  • Prevents downstream display and comparison issues in reporting and metadata tooling.
  • No change to business logic or row counts.

2. Project Item Values – Meta Type Standardisation

Files affected

  • project_item_values_forecast.sql
  • project_item_values_time.sql
  • project_item_values_expense.sql

Change

  • Updated META_TYPE from AMOUNT to SALES.

Reason

  • Aligns financial value semantics across Project item value views.
  • Distinguishes commercial sales-related values from generic numeric amounts.

Impact

  • Improves consistency for value classification and aggregation.
  • Supports clearer filtering and interpretation in downstream analytics.
  • No structural changes to keys or measures.

3. Project Meta Dates – Meta Type Reorganisation

File affected

  • project_meta_dates.sql

Change

  • Reorganised META_TYPE groupings into:
    • DELIVERY
    • LIFECYCLE
    • AGREEMENT
    • DERIVED

Reason

  • Provides clearer semantic grouping of date attributes.
  • Improves discoverability and interpretability in metadata-driven tooling.

Impact

  • No loss of attributes.
  • Enhances clarity for consumers and supports structured lineage and documentation.

4. Person Absence Item Views – Join Binding Improvements

Files affected

  • person_item_dates_absence.sql
  • person_item_values_absence.sql

Changes

  • Removed EMP_NO as a code attribute from Values and Dates item tables.
  • Reinforced OBJECT_SEQ join binding within the code generator.

Reason

  • EMP_NO is a code and cannot be CAST as FLOAT or DATE
    • Latent Error caused by Join confusion
  • Strengthens consistency across generated SQL.

Impact

  • Significant internal improvement to the code generator and attribute lineage editor.
  • More robust and predictable joins across item, meta, and core views.
  • Improves maintainability and accuracy of lineage visualisation.
  • No impact to externally exposed identifiers.

Leave a Comment