I could understand if Appsmith version differences were the culprit, but I exported and then attempted to reimport an unadulterated “My first application” and received the same error.
Present versions:
online: v1.8.14-SNAPSHOT
on prem: v1.8.15
@ bfegley, thanks for reporting this. Just to clarify, is it the on prem, v1.8.15 that is having issues with imports? Can you import the same file successfully on our cloud?
Happy New Year, @GreenFlux! I’m receiving validation failures for both “Appsmith v1.8.14-SNAPSHOT” (your cloud, “online”) and “Appsmith Community v1.8.15” (Docker container, on prem). I’m unable to import any application that I export from these environments to the same environment or across environments.
Frankly, I never had success with Appsmith’s export/import feature, which is one reason I’ve been using the mongodump/mongorestore (database migration) route. However, with the update to v1.8.15, even database migration seems to be problematic, which is why I decided to re-examine application export/import. Bottom line, I’m just looking for a reliable “version proof” (non-breaking) application backup/restore process. I had been following the guidance at Migrate Applications | Appsmith.
@bfegley can you please share the application json file to debug this further. If this contains the sensitive data you can DM me the file or share it on support@appsmith.com?
Hello, @Amelia! I want to confirm that you received the files I sent you via email on January 27th.
Even without those files, for me, simply clicking on “New” button in the workspace at Appsmith, exporting the resulting application (without editing it), and then importing it (into the same workspace, with or without deleting from the workspace first), produces the same “Validation Failure(s)” message that initiated this thread.
Failure to import remains concerning and an impediment to further use of Appsmith for me. Assuming that others are not experiencing the same issue, please advise if there’s anything I can rectify on this end. Thanks much!