Selection of ordinances
edited March 3, 2021 in Suggest an Idea
M Livingston said: Currently the system forces the user to select all of the ordinances (except sealing to spouse) for temple work. It is specifically sealing to parents that is problematic for me. For example, when I'm submitting the ordinances for a cousin and the cousin's spouse, the system forces me to select sealing to parents for the cousin's spouse. These parents may not have very much information attached to them or it may be speculative. They are certainly not in my direct family tree on which I try to focus. On the request ordinances screen, you are given the false impression that individual ordinances can be selected. I do understand that ordinances need to be performed in order. I would like to request that consideration be given to separating SP from the other ordinances in the same way SS is handled. Thanks for the opportunity to put forward my suggestion. We're all in this together. Stay safe. Regards Margaret
Tom Huber said: There is what seems to be a common misconception about the sealing of children to their parents (SP).
The SP ordinance belongs to the child, not the parents. and like sealing to spouse, the vicarious ordinance work for the parents does not have to be completed before the SP is performed. Once the parent's individual ordinances have been completed, including sealing them together, only then does the previously completed SP ordinance take effect.
Note the following highlighted words from the article "Correct order of temple ordinances" at https://www.familysearch.org/help/hel... (you must be a member logged into FamilySearch to view this and other articles dealing with ordinances)
Please perform temple ordinances in the correct sequence. Perform individual ordinances before sealings. The FamilySearch Family Tree website does not clear ordinances if prerequisite ordinances have not been cleared or performed.Note that "if possible" and "Whenever possible" does not mean "must".
The correct sequence of ordinances is as follows:
* Sealing of a husband and wife and sealing of children to parents (if possible). Whenever possible, parents should be sealed to each other before the children are sealed to the parents.
Although vicarious ordinances performed out of sequence are valid, they become effective only after the prerequisite ordinances are completed.
Ron Tanner in one of his live sessions on Facebook stated that "we do not want any of a person's ordinances to be left uncompleted."
Note the following highlighted section from the article "Why was a sealing ordinance done out of order?" at https://www.familysearch.org/help/hel...
While ordinances should be completed in the correct sequence, you may find that sealing-to-spouse ordinances have been done before the individual ordinances.You are authorized and should complete the proxy sealing-to-parents ordinance since we are not authorized to reserve and submit the unrelated parents' individual and sealing-to-spouse ordinances.
If a sealing-to-spouse ordinance was done out of order, you should simply make sure that the rest of the ordinances get done. You do not need to report the issue to FamilySearch Support. Nor do you need to redo the sealing. The sealing becomes valid after the individual ordinances are done.
This is also true of the sealing-to-parents ordinance. Since it is listed on the child's individual ordinance card, the process allows you to do the sealing-to-parents without doing the parents' individual ordinances first. As with the sealing-to-spouse ordinance, the sealing becomes valid after the individual ordinances are done.0
M Livingston said: Thanks Tom for your reply. I did already know most of what you explained but had never taken it the step further to include parents on the child's ordinance card even when the data was minimal. I think I got caught up in the details of getting everything correct and missed the bigger picture.
Christine said: If you are unsure about correct parents, you could research to be certain, or after other ordinances are completed unreserve seal to parent.0