26.3.3 Release Notes

Set out below is a summary of the highlights, fixes and improvements in the 26.3.3 cloud version of Angles for SAP.

End User - Fixes and Improvements

FeatureDescription
[05676749] Error 400 shown when adding Item Value (Self) to mixed sublist with Orders and Stock
 
An error 400 would be shown when field Item Value (Self) was added to a mixed sublist with Orders and Stock. This has been resolved.
Angle Execution: Drilldown to Item no longer stays in a loading stateAn issue has been resolved where drilldown to item intermittently stayed in a loading state until the user cancelled and retried. Drilldown to item now loads as expected, without needing to cancel and retry.
Calculated Fields: Sorting on calculated fields in ad hoc angles now works
 
An issue has been resolved where results were not sorted when sorting on a calculated field in an ad hoc angle. Sorting on calculated fields in ad hoc angles now works as expected.
Charts: Unsaved marker clears on all tabs after Save allAn issue has been resolved where the unsaved asterisk remained on an active chart tab after Save all, even though the changes had been saved. The asterisk now clears on all tabs after Save all, without needing a page reload or a second save.
EA4IT: Action History Rows field can now be used as a number in pivots
 
An issue has been resolved where the Rows field of the EA4IT Action History object was stored as text instead of a number. As a result, it could not be used in the Data area of a pivot to compare the number of results over time. The Rows field is now numeric and can be used in the Data area of pivots.
Standard content field ValidityStatus does not have a help textValidity Status is a property moved from code to configuration and helptext is not mentioned in SAPSetting when it was moved to configuration. This has been resolved.

End User - Usability Improvements

FeatureDescription
ITMC: Model timestamp shown incorrectly in WebClient and Overview with UTC +5:30 scheduling time zoneAn issue has been resolved where the model timestamp was shown incorrectly in the WebClient and on the Overview page when the scheduling time zone was set to UTC +5:30. The timestamp displayed the model extraction time with the 5:30 offset added, while the refresh start and finish times were already correct. The problem was introduced in patch release 26.2.5 and affected the WebClient from release 26.3 onward. The model timestamp now shows the expected IST time.
RMS: feature-parity between CTE and legacy engines

Fixed three CTE-only query regressions, so the CTE engine returns the same results as the legacy engine. Legacy stays the default engine, so only models set to CTE were affected.

  • Field formatting ignored on lookup fields: CTE returned raw keys instead of the short name, long name or short (long). This affected select, sort and grouping. Also fixed:
    • Grouping on a lookup with a format, or with a prefix bucket (left1 etc.), now resolves the lookup correctly.
    • In multi-class and followup aggregates, the grouping takes the lookup from the first class that has the field.
  • Hour bucket on a Moment field: CTE grouped on the raw timestamp. It now groups on the hour of the day in seconds, as legacy.
  • Field type for NULL values in multi-class queries: in a multi-class result, the NULL that pads a missing field took its type from global metadata. It now takes the type of the class in the union that has the field.

 

Was this article helpful?

We're sorry to hear that.