The children will absolutely 100% stay attached to the parents.About Synchronization (One-Way,Two-Way), Backup and Replicationīackup / Copy / Mirror "Live" Hyper-V Machinesīackup, Replication Over Slow Connections (e.g. I am planning to change it from Text to Record ID#.Ĭan any of you help with the DO'S and DONT's that I need to follow before doing the change. I believe that sorted everything out for me, but to be honest I put a lot of thought into it first, and I could be forgetting something, so think it through and maybe others will chime in as well.īig thing - make a backup.just in case.Ĭurrently, my tables are using a text field as a primary key. After I changed the key, I went to each child table, changed the related field from text to numeric, then imported from my spreadsheet the correct Record ID (so, I merged on the child entry record ID field, and mapped the old lookup field to what is now the numeric related field. Carefully label these to not get confused.Ĥ. Then I exported each child table with the Record ID of the child table entry AND the Record ID of the parent table. Before I changed the text key, I made a lookup field with the record ID, to all the child tables. You will need to change your related field on your child table to a numeric field, and then fill in that related field with the correct record IDs.ģ.
#Mirrorsync primary key changed full
Also, since QB backs up in the middle of the night, my true worst case scenario was getting a full backup from them and reverting back a few hours.Ģ. This meant minimal data would have been input in case I messed anything up. I did my change early before I thought people would be working. If it's a disaster, just use the copy of the app. Things can go wrong so I would first make a copy of your app including all data. I can't remember everything I did, so I don't want this to be seen as a step by step guide, but some helpful hints:ġ. I was successful, but you need to be careful and I had to do a bit of prep work. Perhaps I am misremembering? Mark has way more experience, so you may be able to ignore everything I wrote below! Mark, I seem to remember it did not re-associate the children when I went from text to numeric (only if I went from numeric to numeric). Your Quick Base Message Original Message:Įdit: I wrote everything below before read Mark's reply.
Then test the drop down for choosing the customer. Then go to the form on the child record and make sure that Customer Name is on the form and Related Customer is not.
For example if the Customer name was the Key field of the Customers table and now you want to go to, then you go to the Related Customer field, remove the (ref) suffix which QuickBase added, and set the Proxy for to be Customer name. Then you will go to each affected relationship to identify a Proxy field for the field.
#Mirrorsync primary key changed update
You will set the Key field and it will give you two scary warnings and then in a blink it will change the Key field and update all the child records so they stay connected to their original parents. Firstly, you can always copy your app and do the change there, just to practice and see in advance what it will do.
0 kommentar(er)
