You're viewing documentation for release 6 (LTS). Looking for a different release?

10Duke Integration Service release notes

Learn about new features, enhancements, and fixed issues in the most recent 10Duke Integration Service releases.

10Duke Integration Service release 2026-03-24.0

Release date: March 24, 2026

Salesforce

Enhancements:

  • Breaking: You can now manage onboarding and role assignment in 10Duke Enterprise using the custom TendukeOrganizationRole field in the Contact object in Salesforce.

    Setting the value of this field to License manager:

    • Adds the contact to the “employees” user group of the organization.

    • Assigns the admin role to the onboarded contact.

    • Grants access to the 10Duke OrgAdmin tool (if you’re providing it for your B2B customers).

    Setting the value of this field to Member:

    • Adds the contact to the “employees” user group of the organization.

    If this field is not used, is empty, or contains any other value:

    • The contact is not onboarded to 10Duke Enterprise.

    Note that this change requires adding the custom TendukeOrganizationRole field to the existing Salesforce integrations. If this field does not exist, no users are onboarded to 10Duke Enterprise.

    The following values are supported for this field: License manager and Member.

  • Account and contact creation have been decoupled. Creating an organization in 10Duke Enterprise now requires only the Salesforce account information. You can choose to add contact details in the initial create events or at a later time to provision users for that organization.

  • You can now optionally control which contacts are onboarded to 10Duke Enterprise based on a value in the custom TendukeOrganizationRole field in the Contact object in Salesforce. When creating or updating a contact, onboarding is only triggered if this field matches a specific value.

    Provide the 10Duke Integration Support team with the value(s) that should trigger the contact onboarding.

    Note that this configuration replaces the previously used configuration with the Level field.

  • You can now configure the language of a user using the custom TendukeContactLanguage field in the Contact object in Salesforce when creating or updating contacts. This allows you to associate a language with a user using the 2-letter ISO 639 language codes. The language code determines the language of the activation email sent to created users. If this field is not used, the default language (English) is used in the activation emails. This feature is disabled by default.

  • Support added for Product ID in the custom license grant object. When a Product ID is provided, it takes precedence over the Product Code.

See more on Salesforce integration.

Bug fixes:

  • Fixed an issue where changes to the start date of an activated order in Salesforce were not reflected in the licenses in 10Duke Enterprise.

  • Fixed an issue where a license grant remained in 10Duke Enterprise if deleted before the associated order was activated.

  • Other minor fixes.

10Duke Integration Service release 2026-01-12.0

Release date: January 12, 2026

Salesforce

Enhancements:

  • The 10Duke Integration Service can now retrieve Account and Contact object data for records created in Salesforce before the deployment of the 10Duke Integration Service. By default, this feature is not enabled.

    The data is retrieved using Account and Contact creation and update events as follows:

    • The Account and Contact data are retrieved when an update event is received for an account or contact that does not yet exist in 10Duke Integration Service.

    • If Account data does not exist in 10Duke Integration Service when a Contact creation or update event is received, the Account data is retrieved if the Contact object is associated with an Account object in Salesforce.

    • If Contact data does not exist in 10Duke Integration Service when a Contact update event is received, the Contact data is retrieved. If the Account data does not exist in 10Duke Integration Service when the Contact update event is received, the Account data is also retrieved if the Contact object is associated with the Account object in Salesforce.

    Note that while data for both Account and Contact object records can be retrieved, no organization is created in 10Duke Enterprise until Contact data is also available for that Account. Organization creation in 10Duke Enterprise is dependent on the availability of the Contact data and is only triggered once a Contact record is successfully retrieved and processed.

    As a result:

    • Account and Contact data can be retrieved by the 10Duke Integration Service.

    • If the account type configuration and configuration for selecting the administrator user are in use, the Account will not result in a visible organization in 10Duke Enterprise until the value for triggering the admin user creation is set and the corresponding Contact data has been successfully processed and associated with the Account object, and the account type that will trigger the customer creation in 10Duke Enterprise is set to one of the configured values.

    • If the account type configuration and configuration for selecting the administrator user are not used, the Account will result in a visible organization in 10Duke Enterprise when the corresponding Contact data has been successfully processed and associated with the Account object.

Bug fixes:

  • Fixed an issue where a user’s phone number was missing in 10Duke Enterprise after receiving account and contact events from Salesforce. All user data is now derived from the Contact object rather than the Account object.

  • Other minor fixes.

10Duke Integration Service release 2025-12-15.0

Release date: December 15, 2025

Salesforce

Enhancements:

  • The 10Duke Integration Service can now retrieve and internally build account data for records created in Salesforce before the deployment of the 10Duke Integration Service. By default, this feature is not enabled.

    Note that data is only created in 10Duke Enterprise when contact information is available. Organization creation in 10Duke Enterprise is dependent on the availability of the contact data and is only triggered once a contact record is successfully retrieved and processed.

    As a result:

    • Account data can be retrieved and prepared internally by the 10Duke Integration Service.

    • No visible output will appear in 10Duke Enterprise until a contact is associated with the account and the required contact data is available.

    Support for retrieving contact data is currently under development and is planned for delivery in a subsequent release. Once available, this will enable the complete end-to-end synchronization flow.

Bug fixes:

  • Other minor fixes.

On this page