Q3 2022 patches

Original release date: 01 September 2022

Apteco software Q3 2022 build
version number
Apteco FastStats Server 5.8.1
Apteco FastStats 1.1.22214
Apteco PeopleStage 1.0.22214
FastStats Designer 1.3.22214
Web Service 1.0.22214
FastStats Service 1.3.22214
Digital Integration 1.0.22214

Patches

15 June 2023

Patch 13: Exception opening modelling environment containing combinations when using FastStats via a launcher

We've found and fixed an exception that occurred when opening a modelling environment containing combinations

The stack trace included the following error message: Could not load file or assembly 'Apteco.Common.FSharp.... strong name validation failed'.

To apply this fix:

  1. Update the FastStats Configurator to version 1.3.22214.82 or later.

  2. Use this configurator version to update the binaries to version 1.1.22214.84 or later.

For further details, see Applying patches for Apteco software.

12 June 2023

Patch 12: Virtual Package misidentifies string literals as files

We’ve found and fixed a FastStats Service issue misidentifying string literals as files within expression virtual variable definitions. This bug occurred when creating a FastStats Service virtual package, leading to some virtual variables failing to update when using a FastStats Designer virtual package post-load action.

To apply this fix:

  1. Uninstall the FastStats Configurator.

  2. Install the FastStats Configurator version 1.3.22214.81 or later, contained within the WebService.zip file.

  3. Upgrade the FastStats Service version to 1.3.22214.78 or later.

For further details, see Applying patches for Apteco software.

26 April 2023

Patch 11: Microsoft Dynamics Authentication Migration

We’ve found and fixed an issue causing an error when using the Microsoft Dynamics Apteco integration.

Microsoft Dynamics WS_trust authentication has been deprecated. We’ve now migrated the Microsoft Dynamics Apteco integration authentication to OAuth2.0. Clients can now successfully authenticate and use the Microsoft Dynamics Apteco integration.

To apply this fix:

  1. Uninstall the FastStats configurator.

  2. Install the FastStats configurator version 1.3.22214.80 or later.

  3. Install the Web Service version 1.0.22214.75 or later, contained within the WebService.zip file.

  4. Upgrade the FastStats32Service version to 1.3.22214.77 or later.

  5. Use the FastStats configurator version 1.3.22214.80 to update the FastStats Binaries to version 1.1.22214.82 or later.

For further details, see Applying patches for Apteco software.

22 March 2023

Patch 10: Export Issue with expression columns and data grid aggregations

We’ve found and fixed an issue with exports in FastStats. This issue causes expression columns to be exported with blank values if the data grid has a column aggregation defined. The expression values look correct when the data is browsed in the data grid but are unpopulated upon export, if the column setting is set to display descriptions.

A workaround for this issue is to right-click on the affected column header(s) of the data grid, and select the change column to display codes option.

To apply this fix:

  1. Uninstall the FastStats configurator.

  2. Reinstall version 1.3.22214.79 or later, contained within the WebService.zip file.

  3. Use this version of the FastStats configurator to upgrade the FastStats Service to version 1.3.22214.76 or later.

  4. Use the FastStats Configurator to update the FastStats Binaries to version 1.1.22214.81 or later.

For further details, see Applying patches for Apteco software.

Note: You only need to install the above patch if you are using a combination of expressions and column aggregations within a data grid, and are exporting the data.

22 March 2023

Patch 9: Behavioural modelling stopping use of current date as scoring date

We’ve found and fixed an error stating ‘FastStatsRequest todayAt specifies invalid DateTime’, occurring when you refresh a Behavioural Model score variable set using the run date as the scoring date.

Steps to recreate:

  1. Use the modelling environment set up for Behavioural Modelling.

  2. Create a selection scenario and some dimensions.

  3. Launch a PWE or Decision Tree model.

  4. Create a Virtual Variable score variable from the model.

  5. Choose the option to use the Run Date as the Scoring Date.

At this point, the ‘FastStatsRequest todayAt specifies invalid DateTime’, error is displayed, preventing the score variable from being generated.

Note: This error is also displayed when you have a previously created score variable (as per above) and refresh it.

To apply this fix:

  1. Uninstall the FastStats configurator.

  2. Reinstall version 1.3.22214.79 or later, contained within the WebService.zip file.

  3. Use this version of the FastStats configurator to upgrade the FastStats Service to version 1.3.22214.76 or later.

  4. Use the FastStats Configurator to update the FastStats Binaries to version 1.1.22214.81 or later.

For further details, see Applying patches for Apteco software.

Note: You only need to install the above patch if you are using a combination of expressions and column aggregations within a data grid, and are exporting the data.

30 January 2022

Patch 8: Invalid Sftp Key reported when using a Private key

We’ve found and fixed an issue causing invalid private keys for sFTP due to upgraded the third party components with stricter sets of connectivity criteria.

This patch allows components to try the higher level ciphers first, then drop down to the next levels.

Note: If you experience any issues with private keys, then please make sure that they aren't password protected and test within FastStats >Users>Right click on a user or Group>FTP Connections.

To apply this fix:

  1. Uninstall the FastStats configurator and reinstall version 1.3.22214.76 or later, contained within the WebService.zip file.

  2. Then use the FastStats Configurator version to upgrade the FastStats Service to version 1.3.22214.73 or later.

For further details, see Applying patches for Apteco software.

25 January 2022

Patch 7: Moving Bing API from Routes to Isochrone due to large numbers of transactions

We've made some changes to the DriveZone/P2P wizards and the Map tool to minimise the risk of incurring charges due to using large numbers of Bing API transactions without having approved them prior to use:

In the DriveZone wizard, if you match to a geographic variable (rather than a latitude/longitude variable), then zone creation is handled with the Isochrone API (rather than the Routes API). This means that the message displayed on the number of transactions used is now correct (as well as the zone creation being faster and more accurate).

In the DriveZone and Point2Point wizards, if you request isochrones that are too large for the Isochrone API and cause a timeout, then a message is displayed stating that you will incur further transaction charges with continued use of the Routes API.

In the Map tool, if you use the old Routes API (because the zone couldn’t be created using the Isochrone endpoint), then a message is displayed requesting approval the transactions used.

To apply this fix:

  1. Uninstall the FastStats Configurator and reinstall version 1.3.22214.75 or later, contained within the WebService.zip file.

  2. Use this version of the FastStats Configurator to upgrade the FastStats Service to version 1.3.22214.72 or later.

FastStats Local users need to install version 1.1.22214.77 or later, contained within the FastStatsLocal.zip file.

For further details, see Applying patches for Apteco software.

Note: You only need to install the above patch if you are affected by the problems as described above.

19 January 2023

Patch 6: Caching Issue with Expressions in Dynamic Virtual Variables

We have found and fixed an issue with certain dynamic virtual variables which could result in incorrect results. The issue only affects dynamic virtual variables that have a text data type and are derived from expressions.

If a variable of this form was used in a subselection then the cached entry would inadvertently convert the definition of the expression to lowercase. This would mean that selections on this variable would have to use lowercase values in order to return any results.

A workaround would be to set the variable to be a static virtual variable instead.

To apply this fix:

  1. Uninstall the FastStats Configurator and reinstall version 1.3.22214.75 or later, contained within the WebService.zip file.

  2. Use this version of the FastStats Configurator to upgrade the FastStats Service to version 1.3.22214.72 or later.

FastStats Local users need to install version 1.1.22214.77 or later, contained within the FastStatsLocal.zip file.

If you are using the Virtual Package post load action option to refresh virtual variables and you could have variables of this type in your system then you should install version 1.3.22214.72 or later of Designer contained within the Designer.zip file.

For further details, see Applying patches for Apteco software.

Note: You only need to install the above patch if you are affected by the problems as described above.

15 December 2022

Patch 5: Issue Returning Current Datetime

An issue with the query component (fs32svr) has been found and fixed whereby sometimes the current datetime would be older than the actual current datetime. For example, the expression today(0) might return yesterday's date. In all cases restarting the FastStats Service would temporarily fix the issue before it would reoccur.

This issue was introduced in the Q3 2022 release and this patch fixes that release.

FastStats components that use the query component (FastStats Service, FastStats Designer, local FastStats) should be upgraded.

To apply this fix:

  1. Uninstall the FastStats Configurator and reinstall version 1.3.22214.74 or later, contained within the WebService.zip file.

  2. Also then need to use the FastStats Configurator to update the FastStats Service to version 1.3.22214.71 or later.

FastStats Local users can install version 1.1.22214.71 or later, contained within the FastStats Local.zip file.

For further details, see Applying patches for Apteco software.

Note: You only need to install the above patch if you are affected by the problems as described above.

15 December 2022

Patch 4: URN now available to use as Reference in Trustpilot

We have enhanced the Trustpilot integration so that you can now choose to use the URN of an individual as the reference ID. Previously, thereference ID could only be a concatenation of the urn and the send ID.

To apply this fix:

  1. Uninstall the FastStats Configurator.

  2. Reinstall version 1.3.22214.74 or later, contained within the WebService.zip file.

  3. Use this version of the FastStats Configurator to upgrade the FastStats Service to version 1.3.22214.71.

  4. Finally, please ensure that the Upgrade Integrations box is ticked.

For further details, see Applying patches for Apteco software.

Note: You only need to install the above patch if you are affected by it.

29 September 2022

Patch 3: Error Serialising/Deserialising XML in all Applications

We have found and fixed an issue which affects all applications within Apteco software when reading or writing XML (such as loading a saved result). This is delivered via the following exception:

Apteco.Common.ValidationException:

  • Unable to generate a temporary class (result=1).

  • error CS1647: An expression is too long or complex to compile

Stack Trace :

  • System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.

  • at System.Text.StringBuilder.ToString()

  • at System.IO.StringWriter.ToString()

  • at System.Xml.Serialization.Compiler.Compile(Assembly parent, String ns, XmlSerializerCompilerParameters xmlParameters, Evidence evidence)

  • at System.Xml.Serialization.TempAssembly.GenerateAssembly(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, Evidence evidence, XmlSerializerCompilerParameters parameters, Assembly assembly, Hashtable assemblies)

  • at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, String location, Evidence evidence)

  • at System.Xml.Serialization.XmlSerializer.GenerateTempAssembly(XmlMapping xmlMapping, Type type, String defaultNamespace, String location, Evidence evidence)

  • at System.Xml.Serialization.XmlSerializer..ctor(Type type, XmlAttributeOverrides overrides, Type[] extraTypes, XmlRootAttribute root, String defaultNamespace, String location, Evidence evidence)

  • at Apteco.Common.XmlSerialisation.XmlOverridesCacheKey.CreateXmlSerialiser()

  • at Apteco.Common.XmlSerialisation.XmlSerialisable.XmlSerializerCache.GetXmlSerializerForKey(XmlOverridesCacheKey key)

  • at Apteco.Common.XmlSerialisation.XmlSerialisationWrapper.ToString(String firstTag, XmlOverrides overrides)

  • at Apteco.Common.XmlSerialisation.XmlSerialisationWrapper.ToString()

  • at Apteco.Common.XmlSerialisation.XmlSerialisableUsingWrapper.ToString(IXmlSerialisableUsingWrapper xmlSerialisable)

  • at Apteco.Common.XmlSerialisation.XmlSerialisableUsingWrapper.ToString()

To apply this fix:

  1. Uninstall the FastStats Configurator.

  2. Reinstall version 1.3.22214.64 or later, contained within the WebService.zip file.

  3. To use this version of the FastStats Configurator, upgrade the FastStats Service to version 1.3.22214.60 or later.

Also, please ensure that the FastStats Client Binaries are updated to version 1.1.22214.60 or later, and PeopleStage Client Binaries to version 1.0.22214.60 or later.

If the issue arises in Excelsior, then uninstall Excelsior and re-install version 2.0.22214.68 or later, contained within the Excelsior.zip file. This issue in Excelsior means that certain FastStats objects cannot be inserted into an Excel worksheet and errors are thrown.

For further details, see Applying patches for Apteco software.

Note: You only need to install the above patch if you are affected by it.

22 September 2022

Patch 2: Decision Tree Issue with Non-Sortable Decodes

A bug has been fixed in the decision tree which prevented the display of some trees which contained splits based on an ordinal selector variable that had numeric, non-zero-padded codes. These are variables where the order of categories has meaning (e.g. bands of a numeric variable) and the code order is changed if they are sorted alphabetically. Codes are typically 0 padded and so can be sorted (e.g. 08, 09, 10, 11) - however without the zero the sort order is changed (10, 11, 8, 9).

The bug only affected trees using this type of variable and only affected the displaying of the tree.

A typical error would be:

Stack Trace :

  • Apt.Disco.Utilities.DiscovererException: Error running Decision Tree: ---> Apt.Disco.Utilities.DiscovererException: Apteco.Common.WrappedAptecoException: The following AptecoException occurred: ---> Apteco.Common.AptecoException:

List of ordinal values is not in ascending order for the dimension:

  • <Dimension Name>. Code 9 followed after 15 at Apt.Disco.Plugins.DecisionTree.Visualisation.Structure.Model.ListGeneratorForOrdinal.CreateListImpl(Int32 maxLength)

:::

To apply this fix:

  1. Uninstall the FastStats Configurator.

  2. Reinstall version 1.3.22214.62 or later, contained within the WebService.zip file.

  3. Use this version of the FastStats Configurator to upgrade the FastStats binaries to version 1.3.22214.58 or later.

FastStats Local users need to install version 1.3.22214.58 or later, contained within the FastStats Local.zip file.

For further details, see Applying patches for Apteco software.

Note: You only need to install the above patch if you are using the Decision Tree tool with variables that have non-sortable numeric decode values and are affected by the above issue.

22 September 2022

Patch 1: Issue with CleverReach Email Broadcasts

We have found an issue with our CleverReach integration in that contacts that have opted-out of mailings with CleverReach could inadvertently be opted back in via a PeopleStage broadcast and therefore, receive unwanted messages.

We have now changed the behaviour so that if PeopleStage is reusing a list then we never re-activate people who have previously been deactivated.

To apply this fix:

  1. Uninstall the FastStats Configurator.

  2. Reinstall version 1.3.22214.62 or later, contained within the WebService.zip file.

  3. Use this version of the FastStats Configurator to upgrade the FastStats Service to version 1.3.22214.58 or later.

For further details, see Applying patches for Apteco software.

Note: You only need to install the above patch if you are using the CleverReach email broadcaster and are affected by the above issue.