I am encouraged with FH V7 that I can produce the type of output that I find suits my needs. I have created some shared facts that will group together many individuals and associate them to one fact.
When I can construct a sentence that I like there are some areas that I can’t seem to get correct. I can create a sentence as such as: • StepSon: {role(single)=stepson}><<br>. This works well but in my family my ancestors were not very creative with naming people. I have many generations, usually about 3, that there was a person identically named in each generation. So I have a John, John, John in succession. I also have some where in the same family that I have a son named John who died in early childhood and the next son born was also named John. Very confusing.
So I was trying to more closely identify each person in the previously illustrated sentence. My goal was to include a birth year and death year to the sentence to clearly identify which John I was referring to. The RIN can technically be used but in trying to create output that is readable that does not do it as well as I would like.
My question is it possible to get the birth and death date from a role person?
I have tried adding this to the sentence: {%CUR_PRIN.BIRT.DATE:YEAR%} but this gets me the birth of the principle and not the role person. Is it possible to get the B date of the role person. I have tried many attempts but all have failed.
Another problem that I have run into (my own doing) is that if I try this: {%CUR_PRIN.BIRT.DATE:YEAR%}{%CUR_PRIN.DEAT.DATE:YEAR%} the first year comes out but the second date comes out as text.
Any help would be appreciated.
* Role persons BDATE
- tatewise
- Megastar
- Posts: 27075
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Role persons BDATE
Sorry, but many users have tried that approach, but it is impossible to add the extra details you want.
It is just not possible to combine {role(single)=stepson} with any other computed value such as {%CUR~WITN.BIRT.DATE%} inside the conditional <angle brackets> and {=CombineText(...)} does not offer a solution because {role(single)=stepson} is not an allowed parameter inside functions.
Anyway, CUR~WITN is invalid in that context, and even if it worked I'm not sure it would cope with {role(plural)=stepson} when there are multiple witnesses.
I suspect the problem with {%CUR_PRIN.BIRT.DATE:YEAR%}{%CUR_PRIN.DEAT.DATE:YEAR%} is you are using it inside conditional <angle brackets> and that is not valid because only one {%...%} is allowed.
There must be only one computed value that either exists or does not exist on which the conditional <angle brackets> make its decision.
You can combine them as {=Text( Text(%CUR_PRIN.BIRT.DATE:YEAR%) . "-" . Text(%CUR_PRIN.DEAT.DATE:YEAR%) )} or somewhat more simply {=LifeDates(%CUR_PRIN%)}
It is just not possible to combine {role(single)=stepson} with any other computed value such as {%CUR~WITN.BIRT.DATE%} inside the conditional <angle brackets> and {=CombineText(...)} does not offer a solution because {role(single)=stepson} is not an allowed parameter inside functions.
Anyway, CUR~WITN is invalid in that context, and even if it worked I'm not sure it would cope with {role(plural)=stepson} when there are multiple witnesses.
I suspect the problem with {%CUR_PRIN.BIRT.DATE:YEAR%}{%CUR_PRIN.DEAT.DATE:YEAR%} is you are using it inside conditional <angle brackets> and that is not valid because only one {%...%} is allowed.
There must be only one computed value that either exists or does not exist on which the conditional <angle brackets> make its decision.
You can combine them as {=Text( Text(%CUR_PRIN.BIRT.DATE:YEAR%) . "-" . Text(%CUR_PRIN.DEAT.DATE:YEAR%) )} or somewhat more simply {=LifeDates(%CUR_PRIN%)}
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
NE researcher
- Silver
- Posts: 9
- Joined: 15 Jan 2021 13:50
- Family Historian: V7
Re: Role persons BDATE
Thank you Mike,
I suspected that this was not possible but thought I would ask to see if some one else had come up with a solution
I suspected that this was not possible but thought I would ask to see if some one else had come up with a solution