The following fixes, enhancements and changes have been made in version 4.1 product update 5.

There is one critical issue resolved in the previous update. If you are upgrading from a version other than v4.1 PU2 please read the breaking change section below.

Check out the updates in the previous updates:

• Product Update 4
• Product Update 3
• Product Update 2A
• Product Update 1
• See what’s new in the initial 4.1 Release

• IMAN-1846 – Sage300 – The Sage300 connect now has the ability to print A/R Statements.
• IMAN-1839 – Changes the default transform id from the internal hashcode to a readable form, representative of the transform type.
• Confirmed support for the new Chromium Edge Browser. Seriously quick, check it out!
  See the full list of supported browsers.

• IMAN-1853 – OAuth Setup – Fixes an issue where the Username field would truncate values over 30 characters.
• IMAN-1852 – Scheduler Page – Would occasionally crash out, not being able schedule new integrations, requiring the IIS Application Pool to be reset. This fix also improves error handling on the page.
• IMAN-1851 – Connector Mapping – Fixes several issues with the connector field mapping: fields not updating, fields could not be swapped, and spurious delete messages.
• IMAN-1849 – Sage300 – Service Manager Documents – Fixes two issues around the update handling on Service Manager documents.
• IMAN-1848 – Sage300 – Purchase Order Import – Fixes an error if a field was not mapped to the Line Number (PORLSEQ) field. This fix also improves the handling of writing line numbers back to the IMan dataset.
• IMAN-1847 – Designer – Fixes/improves the Zoom calculation. In previous versions the area provided to the Design area wasn’t properly scaled to size of the screen for certain browsers. This improves the handling so that the design surface is properly scaled.
• IMAN-1843 – Filter Transform – Fixes an issue where the script/filter expression is clearing the value assigned to the ‘changed’ to drop down value when a Filter expression has an error.
• IMAN-1842 – VBScript – Fixes an issue on the VB Script Control where the expression/script wasn’t saving after an error.
• IMAN-1840 – Sage200 – PLInvoice – An error occured whilst creating the Purchase Invoice. The entry will be discarded. Contract Failure: Instrument must be a PurchaseInvoiceInstrument.
• IMAN-1839 – Fixes an issue where the priority wasn’t properly being set for new transform.
• IMAN-1838 – Email Task – Fixes an issue where a stack overflow/infinite loop would cause the Data Service to crash.
• IMAN-1832, IMAN-1833, IMAN-1834, IMAN-1850 – Auditing – Fix several issues with multithreaded connectors.
• IMAN-1831 – Database Reader – Fix issue where DB Reader would return all records in Preview. The new functionality limits the amount of records.
• IMAN-1829 – Sage200 – P/C Adjustment – Fixes an Object Reference Error.

This (breaking) change is resultant of the issue fixed in Product Update 2.

Flatten, Hierarchy, Translate transforms – In version 4.0 & 4.1 any field in these transforms without a value set would set the field to the it’s default value.

This change reverts pre v4.x functionality so as not to set the field’s value.

The issue caused the following behaviour:

• Integer & Decimal Fields – Unset fields would be set to default value of 0.
• Boolean Fields – Unset fields would be set to default value of False.
• Text & Binary Fields – Not affected (due to the default handling of Text fields).

The following affects would have been seen:

• Expression Based Transforms (Map, Filter, Aggregate) – Not affected.
• Write Transforms – Not affected.
• Connectors – Unexpected fields would have been set/updated causing unexpected errors since the fields will be set with default values.

We believe the impact is low.

If an expression has been added through a Map or Aggregate transform to counter the unknown affects, this logic should still work, due to default field value handling. We recommend however, that you check this still works following installation of this update.

The following fixes, enhancements and changes have been made in version 4.1 product update 4.

The majority of the enhancements centre around functionality used to integrate with different webservices. There are two new functions for performing adboc GET requests outside of the Reader and WebserviceLookup function and four functions encoding and decoding values to and from Base64 format.

These functions combined expand IMan’s webservice capabilties for use with shipping services, handling of document transfer, and the like.

There is one critical issue resolved in the previous update. If you are upgrading from a version other than v4.1 PU2 please read the breaking change section below.

Check out the updates in the previous updates:

• Product Update 3
• Product Update 2A
• Product Update 1
• See what’s new in the initial 4.1 Release

This (breaking) change is resultant of the issue fixed in Product Update 2.

Flatten, Hierarchy, Translate transforms – In version 4.0 & 4.1 any field in these transforms without a value set would set the field to the it’s default value.

This change reverts pre v4.x functionality so as not to set the field’s value.

The issue caused the following behaviour:

• Integer & Decimal Fields – Unset fields would be set to default value of 0.
• Boolean Fields – Unset fields would be set to default value of False.
• Text & Binary Fields – Not affected (due to the default handling of Text fields).

The following affects would have been seen:

• Expression Based Transforms (Map, Filter, Aggregate) – Not affected.
• Write Transforms – Not affected.
• Connectors – Unexpected fields would have been set/updated causing unexpected errors since the fields will be set with default values.

We believe the impact is low.

If an expression has been added through a Map or Aggregate transform to counter the unknown affects, this logic should still work, due to default field value handling. We recommend however, that you check this still works following installation of this update.

• IMAN-1828 – Improves error handling on generation of the audit report.
• IMAN-1827 – Adds several functions to facilitate different webservice interactions.
  
  WebserviceGetBinary, WebserviceGetText – Allow you to perform GET requests against a webservice to obtain Binary (images, rich-text documents, pdfs) and Textual (files) resources.
  Base64DecodeText, Base64EncodeBinary, Base64EncodeFile, Base64EncodeText – These functions allow you to encode and decode values to and from Base64 format. This set of functions help faciliate interactions with webservices to be able to retrieve images, documents and files from webservices and also be able to post to a webservice where a value (image, document, file) has been encoded in Base64.
  
• IMAN-1819 – Sage200 – The Project Cost Adjustment import has been expanded to allow both cost and revenue adjustments.
• Improvements to the Integration Cookbook, adding several articles for common transformation & design patterns, using the different readers and writers.

• IMAN-1820 – Functions – Adds missing function ChrW.
• IMAN-1818 – Sage200 – Nominal Journal Import – Adds missing Goods Amount field.
• IMAN-1817 – Webservices – OAuth Authentication – Fixes an issue where parameters not being escaped on Form URL Encoded type body/request.
• IMAN-1817 – Sage200 – SLInvoice – Fixes the following issue when creating Project Line Items for a Sales Ledger Credit Note. “An error occured whilst creating the Sales Invoice. The entry will be discarded. Contract Failure: Instrument must be a SalesInvoiceInstrument.”
• IMAN-1815 – Sage300 – Adds missing IDRATETYPE field to Customer imports.
• IMAN-1814 – Webservices – Stepped JSON Reader – Fixes an issue where the stepped JSON reader was querying the entry point URL on each transaction. This fix changes the behaviour to query the entry point URL list once.
• IMAN-1811 – Sage300 – Bank Reversals – Fix ‘Record already exists.’ error.
• IMAN-1808 – Scheduler – Fixes an issue where the Schedule Setup interface would fail if a non-administrative user did not have any permitted jobs assigned.

The following fixes, enhancements and changes have been made in version 4.1 product update 3.

The majority of the fixes and enhancements centre around the scheduler, but there is a major improvement to Preview refresh speed and confirmed compatibility for Sage300 2020.

There is one critical issue resolved in the previous update. If you are upgrading from a version other than v4.1 PU2 please read the breaking change section below.

Check out the updates in the previous updates:

• Product Update 2A
• Product Update 1
• See what’s new in the initial 4.1 Release

This (breaking) change is resultant of the issue fixed in Product Update 2.

Flatten, Hierarchy, Translate transforms – In version 4.0 & 4.1 any field in these transforms without a value set would set the field to the it’s default value.

This change reverts pre v4.x functionality so as not to set the field’s value.

The issue caused the following behaviour:

• Integer & Decimal Fields – Unset fields would be set to default value of 0.
• Boolean Fields – Unset fields would be set to default value of False.
• Text & Binary Fields – Not affected (due to the default handling of Text fields).

The following affects would have been seen:

• Expression Based Transforms (Map, Filter, Aggregate) – Not affected.
• Write Transforms – Not affected.
• Connectors – Unexpected fields would have been set/updated causing unexpected errors since the fields will be set with default values.

We believe the impact is low.

If an expression has been added through a Map or Aggregate transform to counter the unknown affects, this logic should still work, due to default field value handling. We recommend however, that you check this still works following installation of this update.

• IMAN-1806 – Confirmed compatibility for Sage300 2020.
• IMAN-1802 – Improves performance on preview by several times on first Refresh of a particular transform. This change also considerably reduces memory usage of the Data/Preview service.
• IMAN-1801, IMAN-1800 – Introduces new facility to either pause a schedule or pause all schedules without having to delete the schedules/stop the Scheduler service.

• IMAN-1799 – Connector – Fixes an issue on versioned connectors when an Duplicate column ‘import’ when attempting to edit field mapping.
• IMAN-1798 – Scheduler – Fixes an issue on preventing Daily schedules being created when the number of days to a value greater than 255.
• IMAN-1796 – Scheduler – Fixes a long standing issue preventing some schedules from being modified.
• IMAN-1794 – Sage300 – Fixes “Accpac API Error 1023 – Tax Tracking Item Classes. Record already exists.” error when creating Tax Entries.
• IMAN-1792 – Sage300 – Adds missing STATUS fields to Canadian and US Payroll Employee imports.
• IMAN-1791, IMAN-1797, IMAN-1807 – Fixes an issue where large jobs with many transforms (100+) would take too long to load and/or convert. This fix also improves general performance in the designer.
• IMAN-1752 – Fixes an irregular, but critical issue with the authentications/logins which would crash the IIS Application Pool, and lose any unsaved work.

The following fixes, enhancements and changes have been made in version 4.2 product update 2.

The majority of the fixes and enhancements centre around connectors, but there is one critical issue resolved in this patch. Please read the breaking change section below.

Numerous updates and improvements have been made to the documentation, specifically the SageX3, Sage300 and Shopify connectors.

This (breaking) change is resultant of the issue fixed in IMAN-1776

Flatten, Hierarchy, Translate transforms – In version 4.0 & 4.1 any field in these transforms without a value set would set the field to the it’s default value.

This change reverts pre v4.x functionality so as not to set the field’s value.

The issue caused the following behaviour:

• Integer & Decimal Fields – Unset fields would be set to default value of 0.
• Boolean Fields – Unset fields would be set to default value of False.
• Text & Binary Fields – Not affected (due to the default handling of Text fields).

The following affects would have been seen:

• Expression Based Transforms (Map, Filter, Aggregate) – Not affected.
• Write Transforms – Not affected.
• Connectors – Unexpected fields would have been set/updated causing unexpected errors since the fields will be set with default values.

We believe the impact is low.

If an expression has been added through a Map or Aggregate transform to counter the unknown affects, this logic should still work, due to default field value handling. We recommend however, that you check this still works following installation of this update.

• IMAN-1789 – Webservice Lookup – Adds the ability to cache the results, vastly improving performance for lookups which make numerous calls to the same resource.
• IMAN-1787, IMAN-1785 – Some miscellaneous improvements to Serial and Lot Number handling, incorporating improved documentation.
• IMAN-1783 – Sage300 Connector – Added ability to receipt multiple purchase orders.
• IMAN-1781 – Sage300 Connector – Added ability to issue the clear lot and serial numbers on O/E Shipments, O/E Invoices & O/E Credit Notes.
• IMAN-1775 – Sage300 Connector – Added ability to create process I/C Dayends.
• IMAN-1774 – Sage300 Connector – Added ability to post prepayments with A/R Invoices.
• IMAN-1768 – Sage300 Connector – Added ability to process specify serial and lot numbers for BOM & Kit components on O/E Shipments.
• IMAN-1745 – Sage200 Connector – Added ability to specify project details on Sales Ledger invoices.
• IMAN-1746 – Sage200 Connector – Added ability to create Project Cost Adjustments.
• IMAN-1744 – Sage200 Connector – Added ability to create/update Project Accounting Projects.

• IMAN-1784 – Sage300 Connector – Added missing (Request Date) field to O/E Order Import.
• IMAN-1778 – Flatten Transform – Fixes an Object Reference error on complex flatten transforms when using either V3 or Cartesian flatten logic.
• IMAN-1776 – Flatten, Hierarchy, Translate Transforms – Fixes an issue with transforms where non-set fields would be processed as default values (see breaking change).
• IMAN-1767 – CSV Reader – Fixes an issue reading data with embedded html.
• IMAN-1767 – SageCRM Connector – Fixes a null reference error on the Opportunity import.
• IMAN-1763, IMAN-1751 – SageCRM Connector – Fixes an issue where the id field not being included on job, resulting in an null reference error.
• IMAN-1741 – Sage300 Connector – Adds missing SYS.CONNECTID field to P/O Contract Costs Import.
• IMAN-1740 – Sage300 Connector – O/E Shipments – Fixes subscript out of range error when updating shipment.
• IMAN-1739 – Sage300 Connector – Fixes/improves optional field handling to insert/set optional fields without having the optional field set to Auto-Insert.
• IMAN-1737 – Fixes a null reference error when upgrading from v3.x to v4.x integrations.
• IMAN-1735 – Fixes an issue when fields with multiple values.
• IMAN-1733 – Sage200 Connector – Fixes ‘Unable to cast transparent proxy to type ‘Realisable.Connectors45.Sage200.IsolatedSage200Logon”.