Sage 300 v3.30

This article outlines the enhancements and fixes that have been made to the Sage 300 solution in Version 3.30.

Note

All solution versions are cumulative, which means enhancements and fixes from previous versions are included in the most current version.

Enhanced

  • Source Mapping

  • Can now map account ranges as well as account groups from Sage 300

    • Can be applied to all companies (*ALL*) or specified companies

    • Can now drill down to the account level in Financial statements

  • Accounts now include segments in the name and can be drilled to from the Main account

  • 3 segment slicers included in all GL Analytics

  • All pipelines are now materialized (set as Table) by default, with warehouse incremental load enabled

  • 'Friendly names' steps removed in all pipelines

  • Better pipeline and column descriptions for some pipelines

  • Lookup pipelines for snapshot tables. Items lookup and Location details lookup

    • These tables typically have columns updated frequently, for example, the On-Hand quantity column for an Item. Looking up columns from a snapshot table would affect incremental loading of downstream pipelines

    • To resolve this, new pipelines have been created from the original pipelines, with only the required columns selected and set to have warehouse incremental load enabled. These pipelines will now be used solely for lookup purposes

  • 9 Segments now packaged as dimensions out of the box

  • Min Date parameter behaviour - Pipelines now filter data > MinDateSourceFilter parameter (previously >=). This ensures that only data after the specified date is included in transactional data (we recommend setting the filter date to a date at the end of the fiscal year)

  • Currency changes

  • GL does not convert amounts to the specified reporting currency. Only functional currency is supported for GL analytics

  • 'Currency rates pivot' renamed to 'Currency rates' for easier understanding

  • 'Currency rates' now a measure group

  • GL analytics have a single slicer selection for Company (cross-company reporting not supported for GL, due to amounts being in Functional currency)

  • Index created on AR Scheduled Payments to improve lookup performance

  • Inventory transactions - Historical warehouse SQL updated to perform better

  • Index created on Purchase orders to improve lookup performance

  • New Item Unit Conversion (ICUNIT) pipeline to convert quantity units to the stocking unit

  • Stocking Unit slicer added to Sales and Purchasing dashboards

  • Various warehouse incremental load fixes

Fixed

  • AR/AP - Invoices that have zero amounts are filtered out. This is so that metrics that use invoice count and aging are not affected

  • AR/AP - Aging is now applicable only for invoices

  • Resolved case-sensitivity issues where columns could not be found due to case differences

  • All purchasing, sales, and inventory quantities are now converted to the item's stocking unit

  • Historical GL Balance pipeline logic updated

  • Aggregated GL Balance includes Adjustments in Period 14 and Closing entries in Period 15

  • Fixed issue in Retained earnings to do with adjustments and closing entries

  • Fixed issue where Purchase order line amount showed outstanding amount instead of original ordered

  • Fixed issue where Purchase invoice line discounts were not handled correctly

  • Fixed issue where Sales invoice line discounts were not handled correctly

  • Fixed issue where Sales invoice line amounts were not displaying for invoices that did not have associate salespersons

Deprecated

  • Removed geocode parameters

    • Geocoding is not supported in Azure, and therefore has been deprecated. This can still be added after model deployment if necessary

  • Create functions script

  • Create geocoding objects script

  • Update - geocode addresses script

  • Update Customer/Vendor geocoding script

  • Optional fields tables. A new data source feature (coming soon) will provide a more intuitive method of adding them

  • Removed Ledger Type slicer from GL analytics

In this section: