Family Historian User Group

I hadn't seen anything posted so thought I would post for awareness.

My Charting Companion 7 stopped working with FH 7.0.3 (FH 7.0.2 is fine)
Took a look and discovered that attributes are now being saved as a "FACT" instead of an "EVEN".
Charting companion will no longer see your "DNA Kit" attribute.
My work around for now is to export to a new gedcom and search and replace "FACT" with EVEN".
Another possible work around would be to convert your "DNA Kit" attribute to an event but I haven't looked into that yet.

Hope this helps someone.

Ron

Ron, sorry, I think you are mistaken.
The change to using the FACT tag instead of _ATTR happened with FH V7.0.0 when GEDCOM 5.5.1 was adopted.
Custom attributes would have never ever used the EVEN tag in any FH version.
Only custom events use the EVEN tag and still do in FH V6.2.7 and FH V7.0.0 through to V7.0.3.
I can guarantee there has been no change to the use of the EVEN and FACT tags between FH V7.0.2 and FH V7.0.3.

The only way a custom attribute would use the EVEN tag is by exporting a GEDCOM file using the Export Gedcom File plugin.
Choose the (Std) Standard GEDCOM Release 5.5 mode and the DNA Kit attribute will get converted from FACT/_ATTR to EVEN with the value moved to a labelled Note. The same applies to all custom attributes.

I know you use that plugin extensively, so I wonder if you may have inspected or used the wrong GEDCOM file by mistake?

You are correct the older working gedcom file I checked did come from an Export Gedcom File.
I went to a proper backup and checked again and sure enough nothing has changed.

I'm back to figuring out why Charting Companion 7 stopped working with FH.
I've sent a support email to CC to see if they can help.

For now the work around still works or Export Gedcom File
Good memory on the plugin usage, that's exactly what happened.

Thanks Mike

I suspect the problem with Charting Companion, common with many other products, is that they don't check the GEDCOM Version in the Header and only support GEDCOM v5.5 as used by FH v6.2 and not GEDCOM v5.5.1 as used by FH v7.0.
That is one reason why the Export Gedcom File plugin is crucial in converting to the GEDCOM version for each product.

I have charting Companion Version 7.2.40 and it works just fine with my FH7 Gedcom file. I do not however, use any DNA refs.

Regards,

Dave

Dave, the issue seems to primarily involve custom attributes. Custom events will be OK.
So if your Project has no custom attributes or they are irrelevant to the Charting Companion charts then they will work.

tatewise wrote: ↑

27 Apr 2021 14:16

Dave, the issue seems to primarily involve custom attributes. Custom events will be OK.
So if your Project has no custom attributes or they are irrelevant to the Charting Companion charts then they will work.

Agreed, I have the custom Attribute "Eye Colour" in FH7 and it is ignored by CC.

Dave

If you want Charting Companion to include those then you must use the Export Gedcom File plugin as explained earlier.

tatewise wrote: ↑

27 Apr 2021 18:56

If you want Charting Companion to include those then you must use the Export Gedcom File plugin as explained earlier.

I have received a reply from Pierre Clouthier at Progeny Software, with a download link to version 8 of Charting Companion, which does recognise custom attributes.

Dave.

Excellent, that is a better solution. If only all product developers were so accommodating!

tatewise wrote: ↑

28 Apr 2021 19:37

Excellent, that is a better solution. If only all product developers were so accommodating!

Yes, just need it to recognise rich text now

Yes, great news! They're very responsive.
I sent the details of the FH version changes to Charting Companion last night and tested the new version today.