BUG-000136560 for Portal for ArcGIS

Bug ID Number	BUG-000136560
Submitted	January 6, 2021
Last Modified	December 20, 2024
Applies to	Portal for ArcGIS
Version found	10.7.1
Operating System	N/A
Operating System Version	N/A
Status	Will Not Be Addressed

Additional Information

Esri is focusing development efforts on the current-generation ArcGIS StoryMaps product and has previously announced that its classic storytelling template, which is currently in 'extended support,' is going to be moved to 'mature support' in October 2023. As a result of this direction, the development team is no longer considering enhancements to the classic templates and is only considering critical-priority bug fixes. This issue is either an enhancement or a bug that has not been classified as critical, so the development team does not plan to address it in the classic story map templates. ArcGIS StoryMaps is being developed with modern technology and design patterns and the benefit of years of feedback received from the storytelling community about Esri’s classic storytelling templates. Although there are issues and no enhancement is to be implemented in the classic templates, many of these have already been incorporated into ArcGIS StoryMaps or are being considered for future updates to ArcGIS StoryMaps. For more information on the classic storytelling template transition plan, see the ArcGIS Blog: https://www.esri.com/arcgis-blog/?s=#&tag=classic-esri-story-maps-transition

Workaround

The steps mentioned in the below article managed to be a workaround for the issue:

https://pro.arcgis.com/en/pro-app/latest/help/sharing/analyzer-error-messages/00294-editable-feature-services-cannot-contain-database-views.htm

To edit other data in the map and only need the data from the view as a reference, do the following:

Remove the view from the map and publish the other data to an editable feature layer.
Create a separate map that contains the view and publish a map image layer or read-only feature layer.

This makes the same data available through web layers while allowing to edit the data, which supports editing.

If the registered data store is an enterprise geodatabase and the view to present joined tables is used to edit, do the following:

Remove the view from the map.
Create a relationship class between the tables you were joining together using the view.
Add the tables that participate in the relationship class to the map.
Publish an editable feature layer.