Don't add the "Event" content type to a list

%3CLINGO-SUB%20id%3D%22lingo-sub-677859%22%20slang%3D%22en-US%22%3EDon't%20add%20the%20%22Event%22%20content%20type%20to%20a%20list%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-677859%22%20slang%3D%22en-US%22%3E%3CP%3EA%20user%20added%20the%20%22event%22%20content%20type%20to%20a%20list%20on%20SharePoint%20Online.%26nbsp%3B%20It%20installs%20some%20columns%20that%20are%20any%20combination%20of%20un-deletable%2C%20hidden%2C%20having%20dependencies%20each%20other.%26nbsp%3B%20After%20deleting%20the%20%22start%20date%22%20column%2C%20the%20list%20becomes%20in-operable.%26nbsp%3B%20Items%20cannot%20be%20added%20or%20modified.%26nbsp%3B%20Removing%20the%20event%20type%20from%20the%20list%20does%20not%20allow%20you%20to%20clear%20these%20columns%20out%2C%20adding%20the%20columns%20back%20does%20fix%20the%20issue%20where%20items%20can%20be%20added%2Fmodified.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20in%20the%20trenches%20with%20PnP%20Powershell%2C%20but%20I%20may%20have%20to%20delete%20the%20whole%20list%20and%20start%20fresh.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20even%20know%20where%20to%20officially%20report%20this%20issue%2C%20but%20I'm%20posting%20it%20here%20so%20maybe%20someone%20else%20can%20avoid%20the%20nightmare.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

A user added the "event" content type to a list on SharePoint Online.  It installs some columns that are any combination of un-deletable, hidden, having dependencies each other.  After deleting the "start date" column, the list becomes in-operable.  Items cannot be added or modified.  Removing the event type from the list does not allow you to clear these columns out, adding the columns back does fix the issue where items can be added/modified.

 

I'm in the trenches with PnP Powershell, but I may have to delete the whole list and start fresh.

 

I don't even know where to officially report this issue, but I'm posting it here so maybe someone else can avoid the nightmare.

0 Replies