I had the exact same issue: when attempting to view a Dataverse table that was imported from a SharePoint List, "something went wrong" would appear, but only if I displayed certain columns. I narrowed it down to a particular column, and realized that this particular column, which was configured in the SPO List as a "choice" column in which the user was required to choose a single item from a list, the "choices" in the SPO list were not actually specified in the column configuration in Lists. Thus, there were rows imported into the Dataverse table where the value in the "Status" column, which is configured to only accept certain values, had invalid values (as the list of accepted values was blank, as it was in the SPO List). I manually filled in the list of accepted values in that field using the table editor, and voila: error went away immediately.
(Possibly worth mentioning: this table was imported from an SPO list that was imported from an Excel sheet. So, the Excel sheet had data validation on that column, which when imported into SPO didn't import the accepted values list from Excel. SPO didn't care and would show the list without issue. Dataverse apparently cares.)
