Home› Welcome to the FamilySearch Community!› Suggest an Idea

Failure of "Individual Card Data" to link to temple data causing Family Report problems

StewartTM
StewartTM ✭✭
February 8, 2021 edited February 8, 2021 in Suggest an Idea

A selection of individuals (not all) have a problem declaring the temple data on the individual information card - any individual with such a problem with temple data being displayed on the individual information card blocks the family being reported on either the "Family" or "Family with Sources" report.

message on the Individual Card when hovering over any ordinance is:

"KEY: fs.temple.ordinance.ERROR_GETTING_ORDINANCES(en)"

Despite the problem and error message on the Individual Information Card - the temple data is correctly reported on the Ordinance tab for the individual.

Attempting to print a Family or Family with Sources report where any member of the family has such a problem with temple data on the Individual Card returns the message:

"We are unable to generate your pedigree pdf at this time. Please try again later."

Feel free to try on LC6R-7BR

and let me know if you get a different result.

Have raised a Problem "Case" - but so far no response from FS.

0

Comments

  • Brett .
    Brett . ✭✭✭✭✭
    February 9, 2021

    StewratTM

    .

    Just a thought ...

    .

    NOT that the ERROR should be OCCURRING ...

    [ Which it should NOT ... ]

    .

    But ...

    That said ...

    .

    The ERROR is POSSIBLY occurring; as, the Parents (ie. in this case, the FATHER) to which SHE was ORIGINALLY "Sealed", have been INCORRECTLY "Merged"/"Combined", out of existence (ie. "Deleted"; but, actually, "Archived").

    .

    In other words, Her ORIGINAL Parents (ie. in this case, the FATHER) were (may have) NOT (been) "Merged"/'Combined" correctly.

    .

    IF, Her ORIGINAL Parents (ie. in this case, the FATHER) were "Merged"/'Combined" correctly; THEN, that ERROR, most likely would NOT occur.

    .

    Still, regardless, 'Yes', that ERROR should be addressed/fixed.

    .

    Again, just my thoughts.

    .

    Brett

    .

    ps: I will "Send" (ie. I will post in your Profile) IMAGES of WHAT I am referring ...

    .

    [ But, just NOT in this "Public" (both, Members of the Church; and, non-members) Forum ]

    .

    0
  • Brett .
    Brett . ✭✭✭✭✭
    February 9, 2021

    StewratTM

    .

    Just a thought ...

    .

    NOT that the ERROR should be OCCURRING ...

    [ Which it should NOT ... ]

    .

    But ...

    That said ...

    .

    The ERROR is POSSIBLY occurring; as, the Parents (ie. in this case, the FATHER) to which SHE was ORIGINALLY "Sealed", have been INCORRECTLY "Merged"/"Combined", out of existence (ie. "Deleted"; but, actually, "Archived").

    .

    In other words, Her ORIGINAL Parents (ie. in this case, the FATHER) were (may have) NOT (been) "Merged"/'Combined" correctly.

    .

    IF, Her ORIGINAL Parents (ie. in this case, the FATHER) were "Merged"/'Combined" correctly; THEN, that ERROR, most likely would NOT occur.

    .

    Still, regardless, 'Yes', that ERROR should be addressed/fixed.

    .

    Again, just my thoughts.

    .

    Brett

    .

    ps: I will "Send" (ie. I will post in your Profile) IMAGES of WHAT I am referring ...

    .

    [ But, just NOT in this "Public" (both, Members of the Church; and, non-members) Forum ]

    .

    0
  • StewartTM
    StewartTM ✭✭
    February 11, 2021

    It seems that problem "cases" are not revewed very regularly these days - appreciate it if FS staff could look at case 07996460.

    This prolem is occuring on multiple individuals - I use the Familywith Sources as my "back-up" mechanism and now this problem is blocking the creation of these reports on many (but not all) of the back-ups I need to make - happening every day.


    0
  • StewartTM
    StewartTM ✭✭
    February 11, 2021

    It seems that problem "cases" are not revewed very regularly these days - appreciate it if FS staff could look at case 07996460.

    This prolem is occuring on multiple individuals - I use the Familywith Sources as my "back-up" mechanism and now this problem is blocking the creation of these reports on many (but not all) of the back-ups I need to make - happening every day.


    0
  • StewartTM
    StewartTM ✭✭
    February 11, 2021

    Has happened with my own parents!

    0
  • StewartTM
    StewartTM ✭✭
    February 11, 2021

    Has happened with my own parents!

    0
  • StewartTM
    StewartTM ✭✭
    February 12, 2021

    This fault has been introduced since 29th January by FamilySearch.


    Let me explain . . . I keep a backup of my work - and any persons work - on my ancestral families of interest by keeping a Family Group Report wih Sources following any changes . . . resulting in over 700 Group Reports without any problems generating the reports.


    For one particular family - LHFJ-GV1 - I took a successful Group Report back-up on 29th Janauary 2021 . . . today - FS is repeating the reported problem - unable to display temple data in the Individual Card details and fails to produce a Family Group Report for this same individual/family.


    Clearly - in my opinion - FS has introduced some change since the 29th January to cause this problem across a growing number of individuals/families that is completely disrupting my back-process.

    0
  • StewartTM
    StewartTM ✭✭
    February 12, 2021

    This fault has been introduced since 29th January by FamilySearch.


    Let me explain . . . I keep a backup of my work - and any persons work - on my ancestral families of interest by keeping a Family Group Report wih Sources following any changes . . . resulting in over 700 Group Reports without any problems generating the reports.


    For one particular family - LHFJ-GV1 - I took a successful Group Report back-up on 29th Janauary 2021 . . . today - FS is repeating the reported problem - unable to display temple data in the Individual Card details and fails to produce a Family Group Report for this same individual/family.


    Clearly - in my opinion - FS has introduced some change since the 29th January to cause this problem across a growing number of individuals/families that is completely disrupting my back-process.

    0
  • StewartTM
    StewartTM ✭✭
    February 17, 2021

    As at 17 Feb 2021 - now fixed by FS - "this was an ongoing issue but our internal experts have since resolved the problem"

    0
  • StewartTM
    StewartTM ✭✭
    February 17, 2021

    As at 17 Feb 2021 - now fixed by FS - "this was an ongoing issue but our internal experts have since resolved the problem"

    0
Clear
No Groups Found

Categories

  • 24.9K All Categories
  • 593 1950 US Census
  • 47.7K FamilySearch Help
  • 100 Get Involved
  • 2.4K General Questions
  • 370 Family History Centers
  • 367 FamilySearch Account
  • 3.5K Family Tree
  • 2.7K Search
  • 3.9K Indexing
  • 477 Memories
  • 4.9K Temple
  • 272 Other Languages
  • 30 Community News
  • 5.6K Suggest an Idea
  • Groups