Logo
Skip to main content
The Updated Timeline for M.Target and M.JobDescription Entity Updates page has loaded.

Content Hub Changelog

Learn more about new versions, changes and improvements for Content Hub

Updated Timeline for M.Target and M.JobDescription Entity Updates

Content HubContent Hub
ImprovementAction required

Based on the findings from canary testing, the timeline for the updates to M.Target and M.JobDescription entities has been postponed by 3 weeks to ensure a seamless transition and maintain high-quality implementation.

The simulation of the change will now be activated on all non-production environments by February 10th. 

Updated timeline:

February 10, 2025 (previously announced as January 20, 2025): 

  • A simulation of the change will be activated on all non-production environments. This simulation will replicate the behavior of the API with M.Target and M.JobDescription no longer available. You’ll be able to preview the impact on all API queries and SDK implementations that have not been updated where needed.

Between March 10 and March 21, 2025 (previously announced as February 24 and March 7, 2025):

  • Entity Created or Entity Updated raw audit events will no longer be available for M.Target or M.JobDescription entities.

  • M.Target and M.JobDescription will be removed from the Triggers framework, causing existing triggers based on these entities to stop functioning.

  • Querying, creating, or updating M.Target and M.JobDescription via /api/entities (for instance, /api/entities/query?query=Definition.Name == "M.Target" or /api/entities/query?query=Definition.Name == "M.Jobdescription") will no longer work.

  • Older SDK implementations relying on these endpoints will no longer function.

  • M.Target and M.JobDescription will be removed as selectable entities from Manage > Entities.

These changes will be rolled out gradually to customers during the release window, but we recommend completing all integration updates before March 17, 2025.

What should I do?

Update your existing integrations (API, base SDK, and Web SDK) to use the new API endpoints as follows:

  1. Find where M.Target or M.JobDescription entity definitions—or any of their properties—are used.

  2. Download the latest SDK packages:

    1. Base SDK - Version 4.2.29 (or latest version)

    2. Web SDK - Version 4.2.34 (or latest version)

  3. Update the API endpoints or SDK commands with the new endpoints/commands as per the following documentation:

    1. API migration documentation

    2. Base SDK migration documentation

    3. Web SDK migration documentation 

During the transition period, both integration options can coexist. You can develop and deploy your new implementation in parallel, as we’ll still be supporting the existing endpoints and SDK implementations during the entire transition period.