In this article


APSIS One Configuration Values

Here's a list of all APSIS One values sent to Microsoft Dynamics 365 CRM:

  • Discriminator for the Section on which the integration was installed.

  • Discriminator for the Keyspace created to use with the integration.

  • APSIS One API Client ID.

  • APSIS One API Client Secret.


Security Roles

The installation package includes one security role which is required to access the entities related to the APSIS One integration. The name of that security role is APSIS Integration User. and it can be combined with other security roles, including both built-in and custom roles.

This role ensures that users with this role have read-only access to the apsis_authentication and apsis_events entities.


Virtual Entities

Virtual entities to show APSIS data are still under development and the list will be extended as new functions are implemented.

Currently, only the apsis_event entity is implemented, which provides a list of Events shown on the Contact Card.

To read more, head over to the MSD Developer Guide on Virtual Entities.


APSIS Authentication Subsystem

The APSIS authentication subsystem is aimed to provide easy access to APSIS authentication token and consists of the CRMK.APSIS.Authentication plugin, registered automatically during the installation, and the apsis_authentication entity.

During installation, several configuration values holding APSIS credentials are pushed. These allow the subsystems to work as intended.

After the configuration, the authentication subsystem provides the APSIS authentication token. Once expired, it can be renewed.

The authentication subsystem is intended to work only for the purpose of integrating MSD with APSIS One, and not for users to interact with directly.

Get the token information as an output by retrieving the apsis_authentication entity.


Next Step

  • Microsoft Dynamics 365: Keeping the CRM Healthy

Did this answer your question?