Previous Releases
Release notes for previous versions of KeyNamics
Last updated
Was this helpful?
Release notes for previous versions of KeyNamics
Last updated
Was this helpful?
2.0.0.12
30/06/2021
Fixed 'Refused to connect message' within KeyNamics when attempting to redirect login.microsoftonline.com due to X-Frame-Options header.
IMPORTANT: This release of KeyNamics requires the browser to support HTML 5 features to allow for secure cross origin frame communication (IE11 or earlier doesn’t support HTML 5). This matches the minimum requirement acceptable as Microsoft themselves don’t support IE11 or earlier for Power Platform apps as documented . This version of KeyNamics will of course work in any modern web browser that supports HTML 5 features. This includes the latest versions of Chrome, FireFox, Edge, Edgium, Opera, Safari, Vivaldi + all mobile versions. This enhancement removes the need for the webresource Keyfax_Completed.html. Support User Local date time fields in any Date Mappings and NOT Time Zone Independent date time fields. (POBL) Added new window.load event to support right clicking within the Keyfax frame.(POBL) Guard against start-up data being posted twice creating 2 log entries.(POBL)
2.0.0.11
01/05/2021
Keyfax completed page (keyfax_completed.html) hosted as a web resource within Dynamics (replaces polling mechanism).
2.0.0.10
05/01/2021
Remove linebreaks and tab characters (to avoid json corruption).
The following performance improvements including minimising WebAPI calls:
Get all configuration settings before attempting launch, rather than re-requesting
Minimise Web API calls - 'configurationId' (i.e. the GUID of keyfax_configuration table's 'WebServiceUrl' row) made global within JS
Handle startup data template entries in keyfax_configuration entity - this precludes accessing the config file, can circumvent permissions issues and improve performance.
Only check once if tracing/logging is enabled.
2.0.0.9
19/08/2020
Support Auto Launch feature.
2.0.0.8
03/07/2020
Support MultiSelectOptionSets as Target field type FetchXml now available for 'Receive From Keyfax' Remove old Import Export column from views Mapping validation bugfix: Add or remove Default from entry that uses fetchxml was insisting Source is supplied If FetchXml fails, or more to the point, returns nothing, ensure Default is used If Target ends with 'dump', output innerxml not innertext and format to json if target contains 'json' Handled new Mode mapping in keyfax_configuration settings, e.g. Responsive Repairs, Defects=RD, General Enquiry,Anti-Social Behaviour=FL Force Repair node to be a json array Ensure timer is always killed offDon't send dump fields in startup as this could be a vast amount of unwanted data if Keyfax is relaunched Support SDK 9.x Ignore inactive configuration settings Clear out GUID values from template
2.0.0.7
30/04/2020
Added Help pane FetchXml bookmarks are all uppercase e.g. BOOKMARK#1 Display username if authentication fails Minor error message enhancements Bugfix handling bookmarks. Bugfix handle all three bookmarks Display error if no map-out entries found. If a FetchXml fails and a default exists, use it and continue Allow numerics in Mapping name Added Comma+Space separator option in Fetchxml
2.0.0.6
14/04/2020
Up to 3 Bookmarks supported in FetchXml queries (enhancement) Support Help Panes and links to further documentation in Help System (enhancement). Handle mixed case Webservice Url setting (bugfix).
2.0.0.5
01/02/2020
Current Form scraping logic (enhancement) Include Keyfax Test Button on Keyfax_configuration entity (enhancement) Catch/ignore errors when casting fails when GUID is handled (bugfix) If xPath errors, add default and continue (bugfix) Handle multiple xPath results and concatenate (enhancement) Don't add blank values into global/entity lists; where different Current Form fields could be mapped (e.g. property/estate/block) this prevents adding duplicate nodes to startup xml.