The numbers are still there somewhere although I only see them when I print a report. When I export a custom report there are now 3 additional columns titled "ID" numbers which are blank.
The new numbers will change for everyone who has a number after a deleted person. To me, they should not be calling the new numbers "ID" as they are not unique to an individual now and are useless as far as I am concerned. Really wish they hadn't messed with that portion of the program and don't understand the logic of doing so.
I want the old identification numbers in both the reports and on FTM....not the new "counting" numbers. The new numbering system is totally useless for identification purposes as they change for an individual therefore not are not a true "identification" number.
Although it was not perfect, I was happy with version 6 and highly recommended FTM to many people. When I exported a report in that version I did get most of the information I needed although there was no option to include the "description" of a fact...I could live with that although inconvenient. Now, in version 7, I do get the old ID numbers which I want but the custom reports don't export properly either. I have done very little lately as there appear to be too many bugs in Version 7. I do realize my issues are minimal compared to others losing trees, information, etc but as a Premium Member it would be nice for things to work correctly. Is there any timeline when we can expect these issues to be rectified at least to the standard Version 6 did? Will paying members be compensated in any way for all the inconvenience they have experienced?
The ID numbers is not actually a fault in our system but something unexpected that happened:
The ID system was supposed to be internal for the family tree builder (we even had complaints about them in FTB 6) and so we decided to hide them in the new version. Appearantley our members decided to use these ID's as an index for their personal work which is surprising for us and we were never expecting this phenomenon. We changed the IDs to better fit our softwares requirements and to optimize it which resulted a lot of mixed feelings - some people were happy to see them gone and other were not.
As for compensation - it depends on case by case basis, our support team tries to identify the issues and to asses how badly did it affect the project of our member. We are trying to be as generous as possible.
Help! I want to sync the family site, both the online and family tree builder versions contain new data, but I get this error, and until it is fixed I am postponing the work on the tree because if it can't be fixed I might have to delete the new version and start all over again..?
Also, the online version contains photos and they show up (also as images matched to the persons), but the on the builder version even though it seems that the photo file is there, I cannot view it at all. Builder version contains added person data.
Individual in Photo - A matching tag (50A377551E7486945285378ED54AF4D0) was found. Tag '50A377551E7486945285378ED54AF4D0' was not added.
Individual in Photo - A matching tag (50A37755211902586A4D169581FC0328) was found. Tag '50A37755211902586A4D169581FC0328' was not added.
Letters appear as jibberish in reports, when special national charaters such as æ ø ö å appear in the name of the source (citations).
As example, if the source is Sjømannskirken (the norwegian seamen's church) the ø will be written in "jibberish".
This should easy enough to reproduce, just make any source use the letters, include the source for some ancestor, generate a descendants report, make sure sources are included (in my case i chose to have them as endnotes in short format) and voila, jibberish text :)
Old silhouettes are located in Program Files\\MyHeritage\\Res\\Placeholders2\\ and Program Files\\MyHeritage\\Res\\Placeholders2\\Hi-Res\\ directories and named _PlaceholderXXX.jpg. New silhouettes have the same names and located in Program Files\\MyHeritage\\Res\\ and Program Files\\MyHeritage\\Res\\Hi-Res\\ directories.
IMO Record Matching to WVR is a total joke. When it first came out, I subscribed, but quickly cancelled my subscription because it gave me nothing but crap. I keep checking to see if they've improved it, but even a year later, it hasn't changed.
Just today, Family Tree Builder told me that there were 272 records for me, so I thought I'd check.
Please note: I have in my record considerable detail - date and place of birth, date and place of marriage, education, etc. The "Deceased" field is not checked (I'm alive and typing this forum post). I have never lived in the UK, and have never served in the military.
Obviously, Record Matching in FTB still passes nothing but the name on to WVR. They haven't improved the filters at all. That they would include death records for a living person is particularly inane. What a waste of time.
Has anybody ever gotten anything of value from this sorry excuse for programming?
I have to agree with your sediments, I'm not finding much value either. I used a competitor's site for similar activities, and found better matches. I thought I had read / seen that MyHeritage bought that competitior out, but if they did, something has changed.