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

Error Code: -2147015424

(2) ShareShare
ReportReport
Posted on by 16
Hi,
 
I recently get a lot of error code -2147015424 in my CRM. I checked the developer guide (https://learn.microsoft.com/en-us/previous-versions/dynamicscrm-2016/developers-guide/gg328182(v=crm.8)?redirectedfrom=MSDN) for that code but couldn't find anything.
 
 
Could someone help me with this? Thank you in advance.
 
 
I have the same question (0)
  • Verified answer
    Daivat Vartak (v-9davar) Profile Picture
    7,835 Super User 2025 Season 2 on at
    Hello HC-16032012-0,
     

    The error code -2147015424 you're encountering in your Dynamics 365 CRM, along with the message "Operation called with invalid attributes in columnSet," indicates a problem with how data is being requested or retrieved within the application.

    Here's a breakdown of what this error typically means and how to troubleshoot it:

    Understanding the Error:

    • Invalid Attributes in ColumnSet: This error specifically points to an issue with the "columnSet" used in a data retrieval operation. In Dynamics 365, when you query for records (either through the UI, JavaScript, plugins, or the Web API), you specify which columns (attributes) you want to retrieve. The error means that at least one of the attributes you've requested is invalid or inaccessible in the current context.

    •  

    Common Causes:

    1. Deleted or Inaccessible Fields:

      • The most frequent cause is that the query is trying to retrieve a field that has been deleted from the entity or that the user doesn't have permissions to access. 

    2. Incorrect Field Logical Names:

      • There might be a typo or an incorrect logical name used for one of the fields in the columnSet. 

    3. Field Type Mismatch:

      • In some cases, the error can occur if there's a mismatch between the expected field type and the actual field type (though this is less common). 

    4. Customizations Issues:

      • Custom JavaScript, plugins, or workflows might be constructing the columnSet incorrectly. 

    5. Form Customizations:

      • Issues with form customizations, such as lookups or subgrids, can trigger this error. 

    6. Dataverse Issues:

      • Occasionally, underlying Dataverse issues can cause this error. 


    7.  

    Troubleshooting Steps:

    1. Identify the Context:

      • Try to determine where the error occurs. Does it happen on a specific form, view, or during a particular action? This will help narrow down the source of the problem. 

    2. Check Recent Customizations:

      • If the error started recently, review any recent customizations (JavaScript, plugins, workflows, form changes) that might be related. 

    3. Inspect JavaScript Code:

      • If you have custom JavaScript, carefully examine the code that retrieves data. Look for any retrieveMultiple or retrieve calls and check the columnSet being used. 

    4. Review Views and Forms:

      • Check the views and forms that are being used in the context of the error. Ensure that all the fields referenced in the views and forms still exist and are accessible. 

    5. Use Browser Developer Tools:

      • Use your browser's developer tools (F12) to inspect the network requests. Look for any failed requests or error messages in the console. 

    6. Test with a Simplified View:

      • Create a simplified view with only a few standard fields and see if the error still occurs. If it doesn't, gradually add more fields to identify the problematic one. 

    7. Check Field Permissions:

      • Ensure that the user experiencing the error has the necessary permissions to access all the fields being retrieved. 

    8. XrmToolBox:

      • If you have access to the XrmToolBox, use it to examine the entity's metadata and verify the logical names of the fields. 

    9. Contact Microsoft Support:

      • If you've exhausted all troubleshooting steps, contact Microsoft Support. They can investigate the issue further and provide specific guidance. 


    10.  

    Regarding the Developer Guide:

    • The developer guide you linked is for Dynamics CRM 2016, which is quite old. While some concepts are still relevant, the error handling and troubleshooting information might not be up-to-date.

    • For the most current developer information, refer to the official Microsoft Learn documentation for Dynamics 365 and Power Platform.

    By following these troubleshooting steps, you should be able to identify the cause of the error and resolve it.

     
    If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.
     
    My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.
     
    Regards,
    Daivat Vartak

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 170 Super User 2025 Season 2

#2
#ManoVerse Profile Picture

#ManoVerse 70

#3
Jimmy Passeti Profile Picture

Jimmy Passeti 50 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans