What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
Site designs & site scripts
Target SharePoint environment
SharePoint Server 2019 (on-premise)
What browser(s) / client(s) have you tested
Additional environment details
CU August 2021 Patch
Issue description
When a calendar list is created in SharePoint 2019 a field with name "Geolocation" is added to the list as well.
The field is sealed so we can't delete it from the calendar list.
According to this article this field should not be added to any lists as you have to programatically add it:
https://docs.microsoft.com/en-us/sharepoint/dev/general-development/how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint ("The Geolocation column is not available by default in SharePoint lists. To add the column to a SharePoint list, you have to write code.")
This field cause problems for SPExport and SPImport of subsites that have calendars with events (content), the calendar(s) will be imported but not the items/events. We have been using SPExport and SPImport in earlier versions of SharePoint (2013 and 2016) where calendar events gets imported as well.
Based on some digging in ULS-log it seems to be related to this Geolocation field in SP2019.
Any reason why this field must be added automatically in calendar lists?
What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
Site designs & site scripts
Target SharePoint environment
SharePoint Server 2019 (on-premise)
What browser(s) / client(s) have you tested
Additional environment details
CU August 2021 Patch
Issue description
When a calendar list is created in SharePoint 2019 a field with name "Geolocation" is added to the list as well.
The field is sealed so we can't delete it from the calendar list.
According to this article this field should not be added to any lists as you have to programatically add it:
https://docs.microsoft.com/en-us/sharepoint/dev/general-development/how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint ("The Geolocation column is not available by default in SharePoint lists. To add the column to a SharePoint list, you have to write code.")
This field cause problems for SPExport and SPImport of subsites that have calendars with events (content), the calendar(s) will be imported but not the items/events. We have been using SPExport and SPImport in earlier versions of SharePoint (2013 and 2016) where calendar events gets imported as well.
Based on some digging in ULS-log it seems to be related to this Geolocation field in SP2019.
Any reason why this field must be added automatically in calendar lists?