Missing DeviceRegistration Table

It is theoretically possible to simply add a table, but there is no guarantee that the application will work correctly, so this is not an option.

I can offer the following option:

  1. Copy all IDs in the application - E9DF3457-FBDF-4D42-A6F3-FDFF2C260FF6.
  2. We will backup.
  3. Remove the application E9DF3457-FBDF-4D42-A6F3-FDFF2C260FF6.
  4. Change in the application Hastings2022 all IDs from application - E9DF3457-FBDF-4D42-A6F3-FDFF2C260FF6.

In this approach, your application will be downtime.

Hi Vladimir, I am not 100% sure I understand you correctly, but I think this is what you mean:

Hastings2021 App (the orginal one) : E9DF3457-FBDF-4D42-A6F3-FDFF2C260FF6
Hastings2022 App (the new one you created) : 49F668C0-314F-EB6F-FF03-8813A8AC1900

In essence we are renaming the new app you created yesterday to the existing one?

  1. Copy all ID’s in the Hastings 2021 app ie - the API Keys etc.
  2. You backup
  3. Remove the application E9DF3457-FBDF-4D42-A6F3-FDFF2C260FF6
  4. Substitute the original API Keys in step 1

Questions:

  1. but the new application will still be 49F668C0-314F-EB6F-FF03-8813A8AC1900 will it not? Or can you also rename the main Application ID to E9DF3457-FBDF-4D42-A6F3-FDFF2C260FF6 so that it is referenced correctly in all the apps with the backendless.init call?

  2. Can we do a new migration so that new data which has been created in the interim time in Hastings 2021 is not lost? ie. You create Hastings 2023 and use that as the source not 2022

  3. Let me check the data first in Hastings 2022 as I still think we have some duplicate data going on.

  4. This still scares me - if something goes drastically wrong can we reinstate the Hastings 2021 app?

  5. How long will downtime be approx? an hour or so?

Mike

OK so just checking what I thought was duplication in some tables and if you look at the Voucher table you will see there are 575 records in Hastings 2021 and 988 in Hastings 2022. If you sort by column Voucher No you will see that there are 2 identical rows for each Voucher Number below Voucher 589 in Hastings 2022 which is wrong. There should only be one row per voucher number as in Hastings 2021 so something not quite right there.

I imagine this is a similar type scenario for LoyaltyPoints and Device Info. The numbers in the table should be identical between Hastings 2021 and Hastings 2022 I think.

In essence we are renaming the new app you created yesterday to the existing one?

Yes.

  1. but the new application will still be 49F668C0-314F-EB6F-FF03-8813A8AC1900 will it not? Or can you also rename the main Application ID to E9DF3457-FBDF-4D42-A6F3-FDFF2C260FF6 so that it is referenced correctly in all the apps with the backendless.init call?

We can also rename the main Application ID to E9DF3457-FBDF-4D42-A6F3-FDFF2C260FF6 so that it is referenced correctly in all the apps with the backendless.init call.

  1. Can we do a new migration so that new data which has been created in the interim time in Hastings 2021 is not lost?

Yes.

  1. This still scares me - if something goes drastically wrong can we reinstate the Hastings 2021 app?

Yes.

  1. How long will downtime be approx? an hour or so?

An hour or so

I did not find in the table a voucher column named voucher number. I found only a voucher ID. It is possible that there are duplicates in this table, although I have not yet found them. You need to know the logic for creating records in this table. I wanted to offer you the option that would give you the most complete data for the entire time of the application.

I have another option for you that will cover everything you want:

  1. Do the export of the latest data in Hastings2021

  2. Create a new application (for example Hastings2021_new)
    As a result, point 1 and 2 of the implementation point are new, fully working, application, in which there is a table of device registration + all data that are identical to the data contained in Hastings2021. I have already created such an application (Hasting2023_identical) and invited you to this application.

  3. We copy the ID application + all the keys from the application (keys2021)

  4. We remove the application Hastings2021

  5. We are changing the keys for Hastings2021_new to keys2021

Hi Vladimir

Yes, thank you for your thought.

I like this idea, just one question - the information in the DeviceRegistration table in Hastings 2022 - where did that come from? and is it possible to put this data into the new option you have outlined as we have it?

Mike

From migration your application v3 (v1-data-2019_01_28_16_36_47.zip)

and is it possible to put this data into the new option you have outlined as we have it?

Yes, it is possible, but there is a nuance that you may not like in this case - for this, you need to export the DeviceRegistration table, but only it cannot be exported, since it has links to other tables (GolfRounds + LoyaltyPoints + Users). Navigate to Manage - Export - select DeviceRegistration and see which tables it is associated with.

I recommend that you take the steps described by me in option number one and in option number two. Get acquainted with the work of export / import in more detail, it will allow you to make a more balanced decision. Also transfer the data you need from Hastings2021.
When you get the result you want, give me an ID application, in which I will change the keys to the keys from the application Hastings2021.

Agreed, I will look at this in more detail and perhaps we can do something on Monday or Tuesday next week.

If we go for option 2 , resulting in an empty deviceRegistration table is it possible for me to manually populate that deviceRegistration from the deviceRegistration table in Hastings 2022. Would that work?

Mike

What does it mean manually? You simply copy the data for the DeviceRegistration table without associated data from two custom GolfRounds, LoyaltyPoints tables and one system table Users? Accordingly, the DeviceRegistration and Users connection will be lost, therefore, I assume that this is not a very good idea. If you go by export, it may work, now I do not have 100% confidence in this, but you have the opportunity to do it and test it.

Hi Vladimir

I have had a think and can we go with this option please resulting in a blank device registration table but information identical to what is currently in Hastings2021.

Many thanks, Mike

Yes.

Do steps 1 and 2. Check to see if everything suits you, then give me an appID.

ok, just importing data now. I have exported data and am now importing that into newly created app rather than cloning Hastings2021. Is that right?

  1. Create a new application (Hastings2021_new)

  2. Export data from Hastings2021 (data.zip)

  3. Import data.zip into the Hastings2021_new.

  4. Check whether everything suits you

  5. Give me an appID

Thanks for spelling it out!

Done.
New Application is actually called Hastings2021_new_2
Application ID: 7EC197E6-B014-6BB7-FF64-CD9839ED9500

and just to confirm Hastings2021 app ID is : E9DF3457-FBDF-4D42-A6F3-FDFF2C260FF6

Can you clone or copy the data from Hastings2021 just before you remove it just in case we have some new users sign up etc in the interim while you do this?

Yes, we will copy data from Hastings2021.

Check Hastings2021 - E9DF3457-FBDF-4D42-A6F3-FDFF2C260FF6

I looked before deleting, it seemed there was no new data. But I created an export file, it is in the root of the Files section - export_2019_07_17_14_40_43_last_from_original.zip

Thanks Vladimir, That looks good to me.