web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Answered

API error when adding columns to contact view

(1) ShareShare
ReportReport
Posted on by 22
Is there anybody that can help me with this error?
 
ModernQueryBuilder: Attempting to add link entities using the old API after adding link entities with the new API. Please use either old or new API
 
I am getting this error when I add an extra column to my contacts views.
 
I have the same question (0)
  • Verified answer
    Amit Katariya007 Profile Picture
    10,409 Super User 2025 Season 2 on at
    This error occurs because the Dynamics 365 system expects consistency between the APIs used to build queries for views. Specifically, you’re seeing this error because the query builder (ModernQueryBuilder) is detecting a mix of "old" and "new" APIs to create the link entities in your query.
     
    This typically happens when:
     
    You have custom code or plugins that modify the view with mixed APIs for linking entities.
     
    Some views or queries were initially configured with an older API, and recent updates introduced components using the new API.
     
    Suggested Solutions:
     
    Download fetch XML from advanced find and examine the view and check if it is having correct details or not. You can also create a new view with same fields and conditions. Compare existing and new view.
     
    If new view is having issues then try below solutions.
     
    1. Check Custom Code or Plugins:
    If you have custom code, plugins, or JavaScript modifying the view, ensure that it uses a consistent API approach. If you’re using the old API in some parts of your code, switch entirely to the new API (ModernQueryBuilder) or vice versa.
     
    2. Recreate the View:
    If the view is system-managed or difficult to troubleshoot, try recreating it from scratch in the Advanced Find tool. This can sometimes clear out hidden inconsistencies between the APIs.
     
    3. Review Solution Imports:
    If you recently imported or updated a solution, check for dependencies or configurations within the solution. Sometimes, imported solutions contain views or link entity configurations that use different APIs.
     
    4. Enable New Modern Advanced Find:
    Ensure you’re using the latest Dynamics 365 features, like the new Advanced Find experience, if applicable, as this can sometimes handle link entities more consistently.
     
    5. Clear Cache or Publish All Customizations:
    After making any changes, try publishing all customizations and clearing the cache to see if it resolves the issue.
  • EL-04100959-0 Profile Picture
    22 on at
    I went with option 2:
    There were a lot of old or deprecated columns included in the view, and after removing the deprecated columns I didn't get the error again.
  • Suggested answer
    Amit Katariya007 Profile Picture
    10,409 Super User 2025 Season 2 on at
    Happy to help you out 🙂 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 70 Super User 2025 Season 2

#2
Gerardo Rentería García Profile Picture

Gerardo Rentería Ga... 43 Most Valuable Professional

#3
Daniyal Khaleel Profile Picture

Daniyal Khaleel 32 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans