Mass update localization and email in ASTPP
By Yevgeniya Suminova on 2021-04-08
Contents
100 records. All at once 1st test
100 records. All at once 2nd test.
Introduction
We will test the update of 100 customers via the new script created for localization mass update.
Here is the document that we followed: https://docs.switzernet.com/3/public/210408-astpp-user-localization/
Preparation
1. We have imported 100 new customers:
· 50 = postpaid
· 50 = prepaid
2. We used the initial code, so all emails were imported with dummy entries that corrupted the data
3. We then have exported data from the database with all necessary fields for the new script (i.e. pricelist_id, counry_id, etc…)
4. We also confirmed that the email data after the import is corrupted in the db.
5. Then in the excel file we have modified the email addresses and set the localization_id as “1”
6. Then with formula we have concatenated all fields and have obtained the format that we will use in the “html” file with the script.
Excel formula:
="["&A1&", "&""""&B1&""""&", "&""""&C1&""""&", "&""""&D1&""""&", "&E1&", "&""""&F1&""""&", "&G1&", "&H1&", "&I1&", "&J1&"],"
7. Then we pasted the result in the “txt” file and saved as “html”
Testing portionally
1. Open “html” file with the script
2. We see that we have 100 records:
3. Press “load()”
4. Press “submit()”
5. Logged in as “admin”
6. We will try to upload now 30 records => from 0 to 29
7. Press “saveall()”
8. System asked me to login again. Logged in as admin again.
9. We see the counter that processes records one by one in one window and in the other one we the interface that is also updated one by one.
10. Saved 29 of 29 of total 100 records
11. We will now check our accounts and see if emails were changed and/or if localization was set correctly.
12. We see that not all accounts were updated. 6 out of 30 did not update.
13. As for the emails, they were changed to correct emails wherever the data was updated.
14. We will no change the records to upload next as following: from 29 to 60
15. Press “load” and “submit”
16. This time we were faster and system did not ask to log in again.
17. it processes the records one by one again
18. At some point we see the following:
But the script continues afterwards.
Maybe there was a mistake in the password. We do not know what kind of mistake that could be.
19. Script stopped at 60th record. This time only 1 record was not updated. This is for sure the “password” problem.
20. Password in “html” file corresponds to the password that is set in billing. The reason of the failure is not understood.
21. We will now upload all the rest from our record (from 60 to 100)
22. Basically, we always see when it is updated successfully with such notification:
23. All 41 records were updated successfully this time.
100 records. All at once 1st test
1. We will now update same accounts that we updated previously, but we will simply set an empty localization. We do this in order to test whether the system will kick us out at some point and if yes, when?
2. Same “Password” mistakes occurred again. We will understand what the problem is there later. Below are all screenshots of all mistakes.
3. It took about 10 minutes and all 100 records were processed. We were not logged out and if there were some mistakes, the process continued till the end.
4. We supposed the system did not like those passwords as they have special characters. But it was wrong, because there are plenty other passwords in other accounts that have same symbols and they were processed correctly.
100 records. All at once 2nd test.
1. We now will change the “localization_id” back to “1” and will again process all 100 records at once.
2. From 61st record it became very slow. We wonder if it is not because we do not navigate in the browser window with our mouse.
3. On 64th record the process looked as if it has frozen completely. But when we got back there with the mouse and moved from one tab to the other, the process retook the usual speed. Interesting…
4. In total 91 records out of 100 processed correctly and localization was updated.
5. In the database we also see that entries are updated (email and localization) wherever it worked
Before: After:
References
https://docs.switzernet.com/3/public/210408-astpp-user-localization/
END
***
© 4z.com