Backendless Support
 
Waiting for user's response

Followup on migration ticket ID 40C2A750-F309-3576-FF70-80270C3BB000

Just wanted to add some context for the ticket that was automatically created. I was trying to migrate my data from Backendless 3 to Backendless 4 and the following ticket was created when the migration failed: ID 40C2A750-F309-3576-FF70-80270C3BB000

If I create a new Backendless app and run the import jobs it works fine. The issue occurs if I then reset the app and delete the tables then try to run the imports again, importing the data file causes a failure.

I'm moving my iOS app to Backendless 4 and created a new Backendless app for it. I migrated my data to the new app so that I could submit the app to apple for approval and they can test it. But I will then need to delete all data and reimport everything once I'm ready to make the new app available for download to make sure I capture all the latest user signups etc in the new database. Unless there is a way to run a delta export and import the delta when my new app goes live I'll need the ability to delete all data from my app then reimport the latest data.

If you have a suggested approach to account for the delta generated between submission to apple for review and the launch data on the app store please let me know.

Edit: I've actually deleted the backendless app that caused the initial problem. I'm going to recreate it and import the data so i can continue with my app store submission process using that app and hope the problem described above is resolved in a few days so I can later clear the data and import the latest. I recreated the problem on another newly created appp so you can investigate, see ticket: ID 84E5BC99-CB31-4195-FF4A-D9BB126F2800

Leave a Comment

Comments (9)

photo
1

Hi Chris,

please provide migration data, send it to support@backendless.com or upload to some application in backendless and then provide application id of this app. Then I will add it to the internal ticket BKNDLSS-16456.

>The issue occurs if I then reset the app and delete the tables then try to run the imports again, importing the data file causes a failure.

when you say reset you mean press the Reset button http://take.ms/TD4L2 ?

photo
1

Yes, I mean pressing the reset button. So I clicked the reset button to wipe out all the users, geopoints, etc then I manually deleted all my custom tables.

photo
1

Meanwhile, you can use next workaround:

1. migrate to the new app

2. go to Manage -> Export and export all data.

3. reset all data

4. import from zip that you got from step 2

photo
1

Any updates on this? And I'm not sure I understand your suggestion is, whats the work around? That's what I was trying to do which resulted in an error. I exported the data from my original app (V3), reset the data on my new app(V4), then try to import but it fails.

photo
photo
1

Hello Chris,

This issue has been fixed and will be available in the upcoming release next week.

Regards, Olga

photo
1

Thanks olga, whats the target fix date? I'm holding my app release until this is in so any info you can provide would be great.

Thanks,

Chris

photo
photo
1

Hi Chris

It's going to be Monday or Tuesday of the upcoming week.

Anton

photo
1

Perfect, that means only minimal delays for me. Thanks!

photo
photo
1

Hi Chris,

The issue should be fixed now, please verify.