Potential bug: date won't change
Best Answer
-
Every date and place in Family Tree has two values: what you entered, and the standardized value. The standardized value can be the same as what you entered, or different, or might not be set at all.
In the example you have, clearly the entered value and the standardized value are different. The date of birth shows the value you entered there (your most recent correction), but the lifespan uses the standardized value of the birthdate.
So just edit the birthdate again, and this time make sure that you select a standardized date that matches the entered date. The standardized date is located just below the entered date when you are editing the date.
0
Answers
-
Please delete your image! The community is NOT private and all posts will show up on any internet search.
It is highly recommended that you keep information on living people to a minimum. No one can see profiles of living persons you create except YOU. Bear that in mind.
0 -
To expand just a bit on Alan's comments, what you are seeing is not a bug but rather a powerful feature of Family Tree that allows more complete, accurate, and complex data than a simple list of "standards" would ever be able to accomidate. I was going to demonstrate how this works, but there is a bit of a bug in editing dates right now that I just posted about
1 -
mod note - Your original question was edited to remove personal information to protect the privacy of living individuals. Please see the Code of Conduct for more details. https://www.familysearch.org/en/help/helpcenter/article/community-code-of-conduct
The title was changed to add specificity and the post was moved to Family Tree https://community.familysearch.org/en/categories/family-tree
1 -
Thanks all. if you look carefully at the image I attached , the surname and ID's/references were removed from the parents & child as I am aware of the requirement for privacy and confidentiality. I kept the dates to show the problem.
Thanks once again to all for your feedback. PS: Alan, I will give that a try and enter a standardized value. If that does not work I will delete the child's record and re-enter/recreate a new record.
cheers
Denis
0