Brendan,
If I do a saved search, and then wish to duplicate one of the found records in order to edit it and add it to the group of found records, if I select the entire record by clicking in the record number on the left, and then choose “Duplicate Record” or Command-D, in Tap Forms 5, the entire record is duplicated as is, and the duplicate shows up in the group of found records. If I do this in Tap Forms Pro, the record is duplicated, but all the fields of type Number are blank in the duplicated record, and the record doesn’t show up in the group of found records.
I suspect this is a bug.
Thanks.
I’ve just fixed this issue and have submitted an update to Apple for review. I don’t know how long it will take them to approve it though.
Thanks,
Brendan
Hi Brendan,
I just updated to Version 1.04 and this issue is fixed, except there is an associated anomaly. If I then delete the duplicated record, it is deleted, but a grey bar with a pound sign (#) appears above the multi-column list view.
If I do a find on a different grooup of records, and then go back to the previous found group, the grey bar disappears.
I guess you’ll fix this in Version 1.05.
Thanks,
Alan
Hi Brendan,
I just installed Version 1.05, and this bug appears to be fixed. Thank you!
Alan
Excellent. Thanks for confirming.
I’m on the 14 day trial of Tab Forms Pro. Using 1.0.6 on iPad, I find that duplicating a record does not copy over numeric field values to the new record. Is there something I need to do to ensure this works?
You’re right, Dave. It’s a bug.
I have both Tap Forms 5 and Tap Forms Pro 1.06 on a 2020 iMac with Mac OS Sonoma. I thought that this issue had been fixed, but after seeing your post, I just tried it again after re-migrating my document from Tap Forms 5 to Tap Forms Pro, and although this works properly in Tap Forms 5, I can confirm that this problem is still there in Tap Forms Pro.
Brendan, when I said above that this issue was fixed, I was checking it on 1.05. Since I am still using Tap Forms 5 until another bug is fixed, I hadn’t checked this issue since I updated to 1.06. Now I see that this problem is back in 1.06.
Oh wow. Ya, I don’t know what happened. I’ll fix it (again)!
Sorry about that.
Hi, Brendan,
Version 1.07 fixes this problem. Thanks.
.
