About this Guide
This guide is designed to help Crelate System Administrators understand the potential user impact of an upcoming release of Crelate. The guide provides additional insights that Crelate System Administrators should be aware of. Crelate provides this guide ahead of scheduled releases to allow Crelate System Administrators time to prepare for and take advantage of new or changing system capabilities.
About Crelate Upgrades
Crelate upgrades are automatic, benefit all users, and usually require no action. Some features need System Administrators to opt-in or opt-out, as they may be off by default for existing customers to minimize disruption. Administrators can control feature activation and should review options to understand impacts and actions needed to enable or hide new functionality based on organizational needs.
Legend
NEW – This is a new feature or functionality. It may need to be enabled and configured.
IMPROVED – This is a change to an existing feature.
CHANGED – This is an existing feature or behavior that has changed, and users need to be aware.
Features
Improved Search Behavior for Activities – IMPROVED / CHANGED
Impact | When searching for contacts, companies, or jobs, the system will no longer include the content of related activities or emails (like notes, messages, or logged calls) in the search results. |
Severity | Medium |
Applies To | Anyone using search |
Action Required | If you previously relied on Contact or Job searches to find specific notes or email content, we recommend using the Activity search instead for those needs. |
SKU | All |
This update improves performance and clarity by narrowing the focus of each search type. The search interface has also been updated to reflect this change—checkboxes now clearly indicate what content is being searched. You can still search for the content of activities and emails directly by choosing “Activities” in the search filters.
New Required Fields – CHANGED
Impact | Starting with this release, First Name, Last Name, and Company Name will be required when adding or updating a record. |
Severity | Medium |
Applies To | Users of the Web Application and Chrome Extension |
Action Required | Users updating contacts manually or through import, will be required to fill out contacts first name, last name, and the company name moving forward. |
SKU | All |
In the coming months, we will be launching many new features including AI Agents and Data Quality assistants. To streamline this, we are taking steps to help customers normalize and cleanup their data. Starting in early May, we will be requiring these fields when importing or updating core records. This helps ensure your records are complete and useful—making it easier to search, match, and communicate effectively with the right people.
Manage User Grid Improvements – CHANGED
Impact | The “User Role” column in the Users area of Settings has been changed to “License Type”. |
Severity | Low |
Applies To | Admins |
Action Required | None – Admins will still be able to sort by this column |
SKU | All |
We’ve updated the Manage Users grid to make it easier to view and manage your team:
The “User Role” column has been replaced with “License Type”, giving you a clearer view of each user’s system-defined access level (like Employee, Admin, or Client Portal User) instead of your custom role names (like Recruiter or Sourcer).
We’ve also added paging to the grid to make it easier to navigate and manage accounts in larger organizations.
Filtering on this grid is no longer possible and users will need to sort columns then search through the pages.
These changes help simplify user management and improve performance in bigger teams.
New Dynamic and Sortables Fields on Contacts – IMPROVED
Impact | New fields are available on the Contacts grid. This includes Full Name (First Last vs Last, First), Primary Owner, Primary Phone, Primary Email, Email Domain, Primary Zip, Primary State, Current Job Title, Primary City. |
Severity | Low |
Applies To | Users of the Web Application |
Action Required | Optional – Users can elect to use these new fields in lists if they would like. To use the new fields, you will need to update your Views. |
SKU | Business |
This is a highly requested feature, and the new fields can be added to grids / lists, used in find and now support sorting!
Twitter renamed to X – CHANGED
Impact | Twitter is being replaced by “X” throughout the UI. |
Severity | Low |
Applies To | All users |
Action Required | None |
SKU | Business |
Twitter was rebranded as X over a year ago, and we are updating our user interface to reflect this change. Candidates sourced from Twitter will now say X (Twitter).
Changed Multiple Duplicate Handling – CHANGED
Impact | We've improved our duplicate detection system to display all potential duplicate contacts or accounts in a list, rather than automatically selecting the first match found. This enhancement gives you greater control over how duplicates are handled by allowing you to review all possible matches before deciding which record to use. You can now make more informed decisions about whether to merge with an existing record, create a new one, or take other appropriate actions based on a comprehensive view of potential duplicates. This feature helps maintain cleaner data by reducing accidental duplicate creation while providing more transparency in the duplicate detection process. The new list view makes it easier to identify the correct match when multiple similar records exist in your Crelate. |
Severity | Low |
Applies To | All users |
Action Required | None – Users will see the new user experience. |
SKU | Business |
New Users can now mark Phone Numbers as Invalid – CHANGED
Impact | A top requested feature, a number can now be marked as “Invalid”. More than one number can be marked Invalid. When a number is invalid its Category Type is set to NULL and the category it was in (Ex: Mobile) is freed up for use by a different number. |
Severity | Low |
Applies To | All users |
Action Required | Optional |
SKU | Business |
API Changes – CHANGED
Impact | Developers may now receive NULL or missing values for certain fields (e.g., CategoryTypeId on Phone Numbers, WhatId on Timeline Items) in Multipass responses. This represents a change from the previous behavior where these fields were always populated. |
Severity | Medium |
Applies To | Developers using the Crelate API |
Action Required | Developers must review and update their integration logic to:
|
SKU | Business+ |
To support the new “Mark Phone Numbers as Invalid” and to optimize data storage, we are making slight changes to how Multipass values are returned. With this coming release, developers should be aware that Multipass values may return NULL or no value in certain instances. Previously, CategoryTypeId was provided on every response, but after this release Phone Numbers can have no CategoryTypeId (which means the number is marked as invalid). Developers should build their code to be handle missing elements (Example WhatId on Timeline Items; or Null/Missing values on CategoryTypeId).
New API Endpoints available in API v3 – CHANGED
Impact | The following endpoints have been added:
|
Severity | Low |
Applies To | All users |
Action Required | None – These are new endpoints and are now available for use |
SKU | Business |
The Crelate v3 API is now at 100% parity with the old v1 and v2 API. All developers and partners are strongly encouraged to use the v3 endpoints for all new and current development.
IMPORTANT: The existing v1 and v2 API will be sunset in the near future.