Forum Discussion

Ahanney's avatar
Ahanney
Copper Contributor
Jun 30, 2023
Solved

Sharepoint Online error when editing a listitem e.split is not a function

Hello, am having a issue with a list that is used on a daily basis by a team of people. We discovered the other day we can no longer make edits (I am the admin of the site and others with edit rights have the same issue). When we double click on the list item for editing it gives the error below. I have researched online and found advice to try the edit in private or incognito mode and indeed this works. But its not a longer term fix. I also tried to save a new view copy, but it had the same editing error.

Can you advise on how to fix this error? Could it be browser update related?

 

 

  • Hello Ahanney, I'm sure you have solved this a long time ago, but for others who may come by this thread... I encountered this very issue today and, in my case, it was a brand-new list created from an Excel document. I had several columns that I set the type to be Choice. The import did a good job at keeping the values but did not populate the choices. Once I set all the choice options for all the choice columns this problem went away. So, check your choice column settings or possibly any special columns you may have as they are likely the source of the problem. Good Luck!

12 Replies

  • Ahanney's avatar
    Ahanney
    Copper Contributor
    BTW... I have noticed that on one column I have choice pills, but they are not coloring as they should. Is that a clue? On other columns the choice pills color normally for different answers.
    • G_Conrad's avatar
      G_Conrad
      Copper Contributor

      Hello Ahanney, I'm sure you have solved this a long time ago, but for others who may come by this thread... I encountered this very issue today and, in my case, it was a brand-new list created from an Excel document. I had several columns that I set the type to be Choice. The import did a good job at keeping the values but did not populate the choices. Once I set all the choice options for all the choice columns this problem went away. So, check your choice column settings or possibly any special columns you may have as they are likely the source of the problem. Good Luck!

      • Ahanney's avatar
        Ahanney
        Copper Contributor

        Thanks for this reply. I had not in fact solved it. When I checked the fields with multiple values to comply with what was actually in the data, it seemed to work again. Much appreciated!

      • Ahanney's avatar
        Ahanney
        Copper Contributor
        some more detail, the SharePoint list has just over 100 rows. On 80% of rows I get the error above when I double click to edit, the other 20% edit fine. I cannot see any discernable pattern to tell me why the 20% work. This is a very frustrating error.
    • Ahanney's avatar
      Ahanney
      Copper Contributor
      many, but this seems the most relevant... the are 120 lines in the list so nothing major.

      TypeError: e.split is not a function
      at t._getArrayFromSPString (1003.js:1:41937)
      at t._getSelectedKeys (1003.js:1:606390)
      at t._getStateFromProps (1003.js:1:602700)
      at t [as constructor] (1003.js:1:30932)
      at new t (1003.js:1:589105)
      at gr (odsp.react.lib-19e38d22.js:2:50181)
      at Go (odsp.react.lib-19e38d22.js:2:69528)
      at Ks (odsp.react.lib-19e38d22.js:2:112828)
      at wc (odsp.react.lib-19e38d22.js:2:99054)
      at Cc (odsp.react.lib-19e38d22.js:2:98982)
      plt.items-view.js:1 Uncaught TypeError: e.split is not a function
      at t._getArrayFromSPString (1003.js:1:41937)
      at t._getSelectedKeys (1003.js:1:606390)
      at t._getStateFromProps (1003.js:1:602700)
      at t [as constructor] (1003.js:1:30932)
      at new t (1003.js:1:589105)
      at gr (odsp.react.lib-19e38d22.js:2:50181)
      at Go (odsp.react.lib-19e38d22.js:2:69528)
      at Ks (odsp.react.lib-19e38d22.js:2:112828)
      at wc (odsp.react.lib-19e38d22.js:2:99054)
      at Cc (odsp.react.lib-19e38d22.js:2:98982)
      plt.odsp-common.js:1 Refused to get unsafe header "X-SERVICEWORKER-DATA-SOURCE"
      plt.odsp-common.js:1 Refused to get unsafe header "SPRequestGuid"
      plt.odsp-common.js:1 Refused to get unsafe header "X-ServiceWorkerFetchInfo"
      plt.odsp-common.js:1 Refused to get unsafe header "SPSQLQueryCount"
      plt.odsp-common.js:1 Refused to get unsafe header "SPClientServiceRequestDuration"
      plt.odsp-common.js:1 Refused to get unsafe header "X-SERVICEWORKER-DATA-SOURCE"
      plt.odsp-common.js:1 Refused to get unsafe header "SPRequestGuid"
      plt.odsp-common.js:1 Refused to get unsafe header "X-ServiceWorkerFetchInfo"
      plt.odsp-common.js:1 Refused to get unsafe header "SPSQLQueryCount"
      plt.odsp-common.js:1 Refused to get unsafe header "SPClientServiceRequestDuration"
      plt.odsp-common.js:1 Refused to get unsafe header "X-SERVICEWORKER-DATA-SOURCE"
  • Lalit Mohan's avatar
    Lalit Mohan
    Iron Contributor
    Hi Ahanney
    To fix the "e.split is not a function" error in SharePoint Online when editing a list item, you can try these steps:

    1- Clear your browser cache.
    2- Use a different web browser.
    3- Disable browser extensions.
    4- Update your browser to the latest version.
    5- Test on a different machine.
    6- Check for recent SharePoint updates.
    7- Try editing the item using SharePoint Designer.
    8- Contact Microsoft Support if the issue persists.

    Remember to back up your data before making any changes or seeking support.
    • Ahanney's avatar
      Ahanney
      Copper Contributor
      Thanks. Yes I'm basically at option 8 in the list.
  • Steve_Penner's avatar
    Steve_Penner
    Copper Contributor
    There are suggestions in other forums it may be browser update-related. Try using both Edge and Chrome to view your list with their most recent versions/updates of those browsers.
    • Ahanney's avatar
      Ahanney
      Copper Contributor
      Thanks. Yes I had reviewed other forums before coming here. Unfortunately we are not in a position to do that. We are subject to the browser version from a corporate image so cannot simply update to the very latest. I'm guessing we received a browser update last week which SharePoint didn't like. All I can do is push the central IT team to move to the next browser version asap.

Resources