3032695 - Catalog, Share, Recent Stories, Favorites settings will be deleted by overwriting a story with Save As in SAP Analytics Cloud (SAC)

• Catalog, Share, Recent Stories, Favorites settings will be deleted by overwriting a story with Save As.
• After marking a story as a Favorite / Feature file, when saving on top of that story with another copy, the story is removed from the Favorites / Feature file even though the story ID and Story Name has not changed.

SAP Analytics Cloud (Enterprise)

1. Log in to SAC.
2. Go to Files and select a story.
3. Mark the story as Favorite: Managing Files and Folders - topic Mark Files as Favorites
4. Copy the story e.g. to a different folder: select the story - Copy to - e.g. "Test Folder": Managing Files and Folders - topic Move or Copy Files
5. Open the copied story in the "Test Folder", update it with some changes and now save it by overwriting the original story: File - Save As - navigate to the original story - system will recognize that story already exists with the same name and will prompt "Overwrite the existing item?" - select Overwrite
6. The original story will be updated with the new changes, story ID and name will be not changed, however it will be not marked as Favorite and disappears from Favorites list on the Home page.

• This is a by design behavior.
• When a user performs Save As action on a story, system will try to create a new story, and copy over the content from the original story. The system will not copy over other properties like favorite, featured or customized link etc. from the original story to the new story.
• If the story name, that the user provides to save the new story does not exist, the new story will be saved to the folder selected.
• If the story name already exists and the user choose to overwrite, the system will delete the story to be overwritten and reuse the parent folder and the ID to save the new story. This is why the favorite, featured or customized link are not preserved in the scenario when the user is trying to overwrite the original story with the changed copy.
• If the user has chosen to overwrite the story itself, the system will detect it is the same story, and change to perform update content action instead. That is why the behavior is different when the user is trying to overwrite the same story.

• An enhancement request is already opened for the topic: Overwriting story in a single tenant retains catalog, shares, recent stories, favorites
  
• Please, review and vote for it, that you wish to support and plan to take advantage of in your organization. Note: You will be notified on updates regarding ideas you have voted for.

This document and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice.
This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics,Error, Issue, System, Data, User, Unable, Access, Connection, Sac, Connector, Live, Acquisition, Up, Set, setup, Model, BW, Connect, Story, Tenant, Import, Failed, Using, Working, SAML, SSO, sapanalyticscloud, sap analytical cloud, sap analytical cloud, SAC, sap analyst cloud, connected, failure, stopped , KBA , LOD-ANA-ADM , SAC Administration , LOD-ANA-DES , Story Design & Visualizations , Problem