3.0.0.0

Learn what's new with KeyNamics 3.0.0.0.

KeyNamics 3.0.0 introduces Power Pages Portal support and several other improvements and fixes. For further information please also see our blog post.

New

• Support for external, tenant access via KeyNamics for Power Apps portals

• Support for additional processing of KeyNamics data via Power Automate Flows

• A "Test" area accessible via the KeyNamics model driven app now provides Dynamics administrators a sandbox to configure KeyNamics before deployment into production

• A "Sessions" area accessible via the KeyNamics model driven app now allows Dynamics administrators to see details for all launched KeyNamics sessions

• A "Results" area accessible via the KeyNamics model driven app now allows Dynamics administrators to review all results from launched KeyNamics sessions

• Localization support and the ability to override strings presented within both the KeyNamics for Power Apps portals and KeyNamics for Model Driven Apps user interface

• Localization support for KeyNamics for model driven apps

• KeyNamics now supports linked entities within FetchXML queries

• Fetch XML queries within KeyNamics don't support linked entities

Improvements

• Added fireOnChange() method to all fields updated by Receive from Keyfax mappings

• Improved actions previously bound to the keyfax_configuration entity. With KeyNamics 3.0.0 actions are now bound to the keyfax_session entity to ensure Create table permissions are not required for the keyfax_configuration entity within Power Apps portals.

• Removed the PluginProfiler entity dependency within the KeyNamics solution. This could cause warnings upon importing the KeyNamics solution into a different environment without development tools enabled.

• <ResultJson/> element now available within GetResult & GetResults2 SOAP web service response

• Improved performance within KeyNamics for Model Driven Apps with client side caching of configuration settings

Fixes

• Casing issue with Webresource_Keyfax string within KeyNamics

• Empty attributes within FetchXML queries cause issues with multiple targets + support for specifying a target start-up XML element for attributes returned via a FetchXml query

• Decimal data type not being handled correctly within "Receive from Keyfax" mappings for model driven & portal app types

• FetchXML queries that return an OptionSetValue, OptionSetValueCollection, Money or EntityReference attribute type are not being handled correctly within KeyNamics