Family Historian User Group

The standard fact for Child Count only allows for an Attribute for an Individual, so I have created a custom family attribute fact "Child Count family" to pickup a count of children which is linked to both father and mother. This works a treat when I create a family fact manually but gets mostly ignored when I bring the facts over as part of the Gedcom import from TMG (I have to use Gedcom import as the auto import doesn't work yet for FH6).

I have a tag in TMG with the name "EVEN Child Count family" in the Gedcom export field, and I can see text in the Gedcom export from TMG like:
1 EVEN
2 TYPE Child Count family
2 DATE AFT 1386
2 NOTE 7
2 SOUR @S298@
3 NOTE Children of Sir John Stewart of Innermeath and Isabella Macdougall:
4 CONT 1. Archibald Stewart
4 CONT 2. Christian Stewart
4 CONT 3. Isabel Stewart
4 CONT 4. Jean Stewart
4 CONT 5. Sir James Stewart of Lorn d. c 1448
4 CONT 6. Robert Stewart, 1st Lord Lorn d. 1449
4 CONT 7. Alexander Stewart
and while I get a family fact created in FH6, the {value} is missing from the dialog box and the sentence reverts to the installation default for unknown facts ({couple} experienced {label} {date} {place} {their ages}).

Any suggestions for how I bring over the {value} field and fact sentence into FH6?

TIA ... John.

Here is the explanation:

(1) GEDCOM Tag
Although you say you created a custom Family Attribute fact in TMG, the exported GEDCOM uses the EVEN tag, which defines a custom Event. There is no Standard GEDCOM tag for a custom Attribute, so FH uses the custom _ATTR tag. Presumably, the 2 NOTE 7 defines the number of children as 7?

With _ATTR the value follows the tag on the same line just like Individual Child Count:
1 NCHI 3
1 _ATTR 3

So your challenge is to adjust the TMG GEDCOM tag definition for your "Child Count family" fact to use _ATTR instead of EVEN and include the fact Value. Maybe a TMG user can help with this challenge.

Another tactic to try is to use any Individual Attribute GEDCOM Tag such as Child Count NCHI. Hopefully then TMG will include the value after the tag, e.g. 1 NCHI 3. After importing to FH, the NCHI Family Attribute will be treated as an Uncategorised Data Field (UDF). Nevertheless, create a custom Family Attribute fact for Child Count using Tools > Fact Types similar to (2) below, and use the Plugin Change Any Fact Tag to convert the Family UDF to the Custom Attribute.

(2) Fact Sentence
Fact sentences do not form part of the Standard GEDCOM specification, so FH creates a default sentence for your custom fact.
For any imported custom fact FH allows a custom Fact definition to be created in much the same way as TMG.
Use Tools > Fact Types and tick Show Hidden, then any <undefined> custom Facts will be identified in the Visible column and with Fact Set = <none>.
Select the fact Label and click Edit to create a definition which includes a sentence Template. Use the Help for more details.

%FAM.NCHI% and %INDI.NCHI[1]% valid Gedcom and supported by Family Historian, so you don't need a custom attribute, unless you need to add additional information.

Now I never knew that!
However, they are treated differently, because GEDCOM defines them differently.

The INDI.NCHI has a predefined Fact Type for Child Count with a sentence Template and can be added as an Attribute.

But FAM.NCHI has no defined Fact Type so cannot have a sentence Template and is added via All tab using Add Miscellaneous. So in my description above it will be treated as one of the <Defined Tags> not a UDF, but a Family Attribute will still be needed if a Narrative Sentence, or Place, or Date details are required.

Of course with V6 you could add the child count to the marriage sentence or similar if you wanted.