KeyNamics

Frequently asked questions related to KeyNamics.

I noticed KeyNamics installed new Dataverse entities. Can you provide a list of KeyNamics entities and there purpose?

A summary of each KeyNamics entity is provided below...

• Configuration Stores important KeyNamics application settings (start-up templates, Keyfax URL, purge settings & other important settings to control KeyNamics functionality & behaviour)

• Fetch XML Stores FetchXML statements used withn KeyNamics mappings (to obtain data for mappings KeyNamics can execute FetchXML queries against Dataverse entities)

• Mappings Stores KeyNamics mappings (mappings allow you to send data from Dynamics into Keyfax & vice versa)

• Test Stores test records to help test & configure KeyNamics.

• Error Logging Stores log entries for a limited period for every time Keyfax is launched via KeyNamics. This log entry will capture any exceptions or detail any invalid settings, fetch XML statements or mappings.

• Session Stores launch details & metrics for a limited period about each Keyfax session launched from KeyNamics. This table is used primarily to help Omfax Systems troubleshoot and identify any performance bottlenecks within your KeyNamics installation. This entity can also be used to trigger Power Automate Flows whenever Keyfax is launched.

• Result Stores results & metrics for a limited period about each Keyfax session launched from KeyNamics. This table is used primarily to help Omfax Systems troubleshoot and identify any performance bottlenecks within your KeyNamics installation. This entity can also be used to trigger Power Automate Flows whenever Keyfax completes.

I noticed KeyNamics has a dependency on the built-in systemusers entity within Dynamics. Why is this?

KeyNamics requires the built-in systemuser entity to exist within Dynamics as KeyNamics has several entity relationships into the systemuser.id column. For example, every entity within KeyNamics has a CreatedBy & ModifyBy column which has a relationship back to the systemuser entity.

These relationships include...

• keyfax_configuration_createdby

• keyfax_configuration_modifiedby

• keyfax_errorlogging_createdby

• keyfax_errorlogging_modifiedby

• keyfax_fetchxml_createdby

• keyfax_fetchxml_modifiedby

• keyfax_mapping_createdby

• keyfax_mapping_modifiedby

• keyfax_result_createdby

• keyfax_result_modifiedby

• keyfax_session_createdby

• keyfax_session_modifiedby

• keyfax_test_createdby

• keyfax_test_modifiedby

KeyNamics does not require any specific attributes to exist within the systemuser entity but of course the KeyNamics relationships above do depend upon the systemuser.id column. As the systemuser entity is a built-in Dynamics entity this should always exist and generally never be modified. KeyNamics will never attempt to modify the systemuser entity or add or update any records within the systemuser entity.

Does KeyNamics support Dynamics 365 Legacy / Classic Web User Interface?

Microsoft revealed early in 2019 that the Dynamics 365 Legacy Web User Interface would be discontinued in October 2020 with users still on it urged to make the move to the new Unified Interface as soon as possible. KeyNamics fully supports the Unified Interface. If a legacy integration is required, although this is not recommended we can supply a version of KeyNamics to support this. We can assist with any subsequent migration to UI.

My Keyfax launch button isn't appearing on my Dynamics App running under iOS?

To operate on your mobile phone, this will require the Keyfax webserver to be running with TLS1.2 enabled (without this, frames will not operate on iOS).

I want to send the contents of a Field on the current Form to Keyfax for use in scripting. I need to know the Field name, - how do I find this?

You can either ask your Dynamics system administrator or form designer, or you can identify the form fields yourself. For further information please see Mapping Entity Form Fields.

How do I migrate Settings, Mappings and FetchXML queries from one D365 organistation / instance to another?

This is possible by using the Dynamics SDK Configuration Migration Tool;.

As a supplier of KeyNamics, what level of access will I need to your D365 environment(s)?

We don’t believe that 'admin' rights are required as that would grant us more privileges than necessary. However, the account would need the ability to:

• Import a Solution: which can be granted through security Roles

• Publish a Solution: will require ‘Publish Customizations’ permissions, which are often included in standard ‘Customizer’ roles.

• Access Model Driven Apps: For support purposes and assistance with Mappings we’ll need app-specific permissions via the relevant security roles (e.g., Customer Service Representative, etc.).

• Perform further customisation: going forward, within the KeyNamics solution it may be necessary to apply fixes/enhancements but as publisher, I believe we should have these permissions.