Release 76

by

This release delivers the first CDM-compliant Customer Satisfaction view, bringing together legacy CSMS and Customer Thermometer data, with extensions for Dynamics data planned next. Work has also begun to align General Ledger reporting to CDM standards, focusing only on the two views required for finance. In addition, improvements have been made to Customer Orderline reporting, ensuring large order values are handled correctly in CDM views, with legacy views noted as still affected.

What this means for you

  • Customer Satisfaction
    You can now access a unified view of customer feedback across legacy CSMS surveys and Customer Thermometer data. This ensures more consistent reporting, with future releases extending coverage to Dynamics CSMS responses. If you currently use the legacy Customer.Thermometer view, please plan to switch to the new Customer.meta_codes_satisfaction.
  • General Ledger
    Finance reporting will soon be streamlined to two CDM-aligned views (GeneralLedger.Transaction and GeneralLedger.PeriodBudget). Access will be controlled, so expect an invite-only model. This reduces duplication and ensures consistency with finance standards.
  • Customer Orderline
    Large order values which appear in the data in scientific notation (e.g. 1.44E08) are available in CDM views. This resolves errors previously encountered in legacy views. If you continue to use older views, you may still experience decimal conversion issues. Migration to the CDM views is recommended for reliability.

Customer Satisfaction

This release targets the replacement of Customer.Thermometer with a CDM-compliant view as part of the CSMS project development.

  • The new view now incorporates legacy CSMS data (external & internal) alongside the original Customer Thermometer data.
  • It is intended that this will be appended with the current CSMS data from Dynamics in a subsequent sprint.
  • The new DataMart view Customer.meta_codes_satisfaction contains the main elements of the questionnaire, including:
META_TYPEATTRIBUTE
CONTEXTSOURCE
CONTEXTTYPE
CONTEXTMILESTONE
OWNEREMAIL_DESC
OWNEREMAIL
CONTEXTPROJECT_ID
CONTEXTPROJECT_DESC
CUSTOMERNAME
CUSTOMEREMAIL_DESC
CUSTOMEREMAIL
METRICSCORE
OUTCOMEWON_LOST
OUTCOMEREASON
RESPONSECOMMENT
RESPONSECUSTOMER_CONSENT
OWNERCOMPANY
OWNERCOUNTRY
RESPONSERESPONSE_ID
RESPONSEDATE
CSATSCORE_RAW
CSATSCORE_TYPE
CSATSCORE_UNIFIED
CSATNPS_CATEGORY

Future Work (next sprint):

The following fields relate to the current Question 9 and form a satisfaction matrix. These will be delivered separately in Customer.item_value_satisfaction:

  • METRIC.SUITABILITY
  • METRIC.WORK_AGAIN
  • METRIC.VALUE
  • METRIC.TIMELINESS
  • METRIC.FLEXIBILITY
  • METRIC.QUALITY
  • METRIC.PROFESSIONALISM
  • METRIC.COMMUNICATION

General Ledger

  • The General Ledger views are being up-revved to CDM standards.
  • It has been confirmed that only the following are required for reporting:
    • GeneralLedger.Transaction >> GeneralLedger.Item_Value_Transaction
    • GeneralLedger.PeriodBudget >> GeneralLedger.Item_Value_PeriodBudget
  • This reduces the development scope significantly.
  • These views will likely follow the finance-restricted route and will be available by invite only.

Customer Orderline

  • On 11 August, an order NET_AMOUNT_VALUE exceeded the decimal threshold in IFS and was delivered as 1.44E08.
  • This scientific notation was anticipated in the CDM views.
  • However, legacy views still attempt to convert to decimal, where 1.44E08 is treated as text and therefore causes errors.

Affected legacy views:

  • customer.orderline_202404
  • customer.orderline_202405
  • customer.orderline_202406
  • customer.orderline_202409
  • customer.orderline_202411
  • customer.orderline_202501
  • project.customerorderline_202406
  • project.customerorderline_202407
  • project.customerorderline_202409

Leave a Comment