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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics 365 | Integration, Dataverse... / Error message Cannot r...
Microsoft Dynamics 365 | Integration, Dataverse...
Suggested Answer

Error message Cannot read properties of undefined (reading 'map')

(1) ShareShare
ReportReport
Posted on by BusyIntelligence 562

Since a couple of weeks several users see errormessages like "Cannot read properties of undefined (reading 'map')".

This occurs when the filter or sort a view, e.g. My contacts.

Strangely some of the times the sorting works fine when the user uses his laptop screen, but results in the error when the window is opened on his second monitor.

Most of the times the view just remains empty as if there are no records to show, but the error shows up after we click on the refresh button above the view.
It first says "error loading control". After clicking on that the errorlog can be opened containing:

Error Details: TypeError: Cannot read properties of undefined (reading 'map')
at t._getColumnState (https://{our url}/%7b637899763480000150%7d/webresources/cc_MscrmControls.Grid.PCFGridControl/PCFGridControl.js:2:1767562)
at t._getConfiguredColumns (https://{our url}/%7b637899763480000150%7d/webresources/cc_MscrmControls.Grid.PCFGridControl/PCFGridControl.js:2:1998787)
at t.getDerivedStateFromProps (https://{our url}/%7b637899763480000150%7d/webresources/cc_MscrmControls.Grid.PCFGridControl/PCFGridControl.js:2:1988447)
at pi (https://{our url}/uclient/scripts/vendor.js?v=1.4.4266-2205.2:9:48334)
at Ha (https://{our url}/uclient/scripts/vendor.js?v=1.4.4266-2205.2:9:70314)
at Ul (https://{our url}/uclient/scripts/vendor.js?v=1.4.4266-2205.2:9:112369)
at Eu (https://{our url}/uclient/scripts/vendor.js?v=1.4.4266-2205.2:9:98325)
at ku (https://{our url}/uclient/scripts/vendor.js?v=1.4.4266-2205.2:9:98253)
at xu (https://{our url}/uclient/scripts/vendor.js?v=1.4.4266-2205.2:9:98116)
at pu (https://{our url}/uclient/scripts/vendor.js?v=1.4.4266-2205.2:9:95103)

Anyone has an idea what happens here?

Kind regards,
Maurits

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at

    Hi BusyIntelligence,

    Maybe you can clear browser cache or change other browsers to test it.

    Have you updated your Dynamics in the meantime?

    You can open one ticket to Microsoft support, which can help you solve the question:

    https://admin.powerplatform.microsoft.com/support 

  • Mehdi Chemseddine Profile Picture
    Mehdi Chemseddine 110 on at

    Hi,

    We have the same problem in 2 of our environments, sorting/filtering a column in most views leads to this error;

    Dynamics is updates and clearing the cache didn't help.

    If you found a solution I'll be more than happy to hear it before openning a ticket to MS.

    Thanks.

  • Rafael Pennese Profile Picture
    Rafael Pennese 25 on at

    Hi There

    I have exactly the same issue here: I tried different browsers, flushing cache, and there doesn't seem to be a consistent behavior...The issue occurs randomly...

    It may have to do with filters as the views where this happens have complex queries.

    I've just created a ticket with Support. I'll update this thread to give you any news I receive.

  • Suggested answer
    Rafael Pennese Profile Picture
    Rafael Pennese 25 on at

    Hi Everyone

    I've just spoken with the support team and there are some good news: this is indeed a but and it's on the current roadmap: ETA August 22 2022 (exact date depends on your region).

    In the meantime, a workaround is to disable the "modern read-only grid experience" un PowerApps features:

    pastedimage1657872187130v2.png

    A small regression compared to the newest view control, but more stable...

    Hope this helps!

  • Suggested answer
    Mehdi Chemseddine Profile Picture
    Mehdi Chemseddine 110 on at

    Hi,

    Thanks for sharing. This seems to solve the issue; 

    What I found out, is that it was some columns with the attributes 'issortable' or 'isretrievable' set to false; I had to go to views remove the concerned columns, save & publish then put them again. this worked for most of them, except one field which persists and didn't changed; 

  • Rafael Pennese Profile Picture
    Rafael Pennese 25 on at

    Update: the bug fix has already been pushed by Microsoft! Changes are available in my region (Europe) and will be rolling out to other regions over the summer.

  • Mehdi Chemseddine Profile Picture
    Mehdi Chemseddine 110 on at

    I confirm that the fix was applied.

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
Siv Sagar Profile Picture

Siv Sagar 93 Super User 2025 Season 2

#2
#ManoVerse Profile Picture

#ManoVerse 76

#3
Martin Dráb Profile Picture

Martin Dráb 66 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

Identifying an Org as CDS or Dynamics
Get batch job history log from D365 FO to Power Automate
Gross and Net Weight of Shipments feeding back into Sales Order (from External Source)

Product updates

Dynamics 365 release plans