Why do the community sheets created by the users no longer work or disappear, after the app is changed and republished by developer?
The QS app is created by the developer and published to the stream. App users or clients now start to create their own sheets and bookmarks and share them with the other App clients. The problem occurs when the developer makes changes to the app and republishes it to the stream. The app clients no longer see their created and shared sheets that are tied to that original app. The users now need to start working with the republished app and build those sheets all over again. This is very frustrating for the app clients.
Is there a way to prevent this from happening when the developer makes changes to the app? How do we keep these users sheets working with the revised app?
Looking forward to responses and to see if others are having this same issue.
Re: Why do the community sheets created by the users no longer work or disappear, after the app is changed and republished by developer?
The objects that are created by the users of the App; These objects belong to the user and become part of the App? Can these objects then be reused by the developer of the app and or the user of the App?