Local Storage Database problems when Migrating from old SAP Appgyver

[josh_pinto]

Hello,

We have been developing a web application in SAP Appgyver over the last few years but we ran into an issue recently regarding local databases when migrating our app to the new SAP Appgyver Community Edition.

In our app (ID: 72530), we have several databases which were created in the old Appgyver platform as “local storage” databases. But when we imported the app into the new SAP Appgyver Community platform, some of our local storage databases were now categorized as “Client-side storage”, while others were labeled as “On-device storage”. Additionally, in the new platform, the only type of local storage database that can be newly created is on-device storage, leading us to presume that this is the new standard local storage database type.

Below is a screenshot of the new SAP Appgyver Community Edition platform showing the two types of local storage databases in our app:

In the web preview of our app, we found that we were successfully able to create and get records from both “client-side storage” and “on-device storage” databases. However, in web app builds, we were unable to get or created records from “client-side storage” databases and received the error: {"code":"unknown","status":-1,"message":"TypeError: Cannot read properties of undefined (reading 'id')","rawError":{}}. 

Through testing, we found that local storage data entities that were not successfully converted to “on device storage” classification during migration did not work in web builds and that in other test apps we created, the Import process was able to successfully convert local storage databases to “on-device storage” databases which worked in web builds.

We are writing this message to inquire and ask the SAP Build Apps team or community to assist us with resolving this issue which is preventing us from deploying the latest builds of our application. We are willing to share the exported app files if needed to help the team discover what is causing this migration error which is causing the local storage problems.

Thank you in advance,

Josh Pinto

[EsmeeX]

Hi Josh, thanks for reaching out. We are looking into a way to convert these resources. I'll update here when we have a solution.

[josh_pinto]

Thank you, we are looking forward to having this issue resolved

[josh_pinto]

Hello Esmee,

We wanted to inquire in case their have been any new information/discoveries made about why this issue might be occurring.

Thank you,

Josh Pinto

[EsmeeX]

Hi Josh. It seems that with the migration, the old type resources won't convert automatically, so the safest bet would be to recreate the resources as on-device storage types. Please let us know if this resolves the issue.