Family Historian User Group

I'm not aware of other users having the problem you describe. I thought you were using AS to capture most types of Source. AS ensures the correct Individual record Facts cite the Source record. Your problem description seems to suggest that only the KeyPerson will be associated with the Source. That...

The proposed solution would result in an ongoing issue. It would require constant maintenance and would not look all that "presentable" in diagrams and reports. Why an ongoing issue? The automatic expression would add the Record Id to every Source record Title. So just add the Record Id t...

Sorry, I was mistaken and my suggestion won't work. The {=RecordId()} function returns the Record Id of the Source record, not the person. I thought the Name type of metafield was a pointer to the Individual record, but I was wrong. So there is no method I can think of that will automatically provid...

I assume you are talking about the Record Title Format: expression and a metafield {KeyPerson} with type Name.

{=RecordId(%SOUR.~NM-KEYPERSON%)} will return the Record Id number.

Yes, it is another example of FH inconsistencies. Only three of the qualifiers display both Lat & Long, and the Preferences options match those three. The Lat/Long data entry dialogue adds a fourth option which has no matching qualifier. Of the other six qualifiers, three only display Lat and th...

Ah! Yes! Ignoring the Lat/Long Qualifiers in that dialog would appear to be a bug. The default display format is governed by the Tools > Preferences... > General tab, Latitude & Longitude Format: setting, which defaults to Degrees, Minutes, Seconds but also allows Degrees (decimal) and Numeric. ...

Welcome to the FHUG. The key to understanding how to make such changes is to use the Data Reference Assistant (DRA). I suspect you are customising the Latitude/Longitude column in the Places tab of the Records Window. ( It always helps us if you describe exactly where you are applying the customisat...

The structure in your posted screenshots looks perfect except for one thing. The top folder should NOT end with Project but just be Snelson Database & Armory the same as the others. That is why you are seeing Snelson Database & Armory (Folder: Snelson Database & Armory Project) The 4 key...

Remember that anything entered via AS could have been entered directly in FH although maybe more laboriously.
So once you know where the details exist in FH they can be post-edited after AS has finished.

The amount of each type of record is limited by the maximum Record Id, which is 2,147,483,647.
So your PC will probably reach its memory limits before the max Record Id is exceeded.

See FHUG Knowledge Base Record Identifiers.

FH allows any records to have the same title/name (except Place records).
e.g. Multiple Individual records can have the same Name, and as discussed here, multiple Source Records can have the same Title. It is the Record Id number that is the unique key which differentiates each record.

Those are remnants of the OneDrive corruption. The 'Projects' with Last Updated 1/01/1971 01:00 are invalid GEDCOM files as that is just a default date. However, they cannot be handled by the More Tasks... options because they all share the same folder. The fix must be applied by using Windows File ...

IMO the Source Title should not refer to the Fact it ratifies but to the Source Document. Also, it is rare for a Source Document to ratify only one Fact, so which one do you choose? e.g. Birth Certificate ratifies Birth Event, the person's Name, parent Names, Address and Occupation. Thus if the Sour...

BTW: A shortcut to Help on the Focus Window is to hit the F1 key (which is a standard Windows feature). There the Help page says: Next to each displayed relative of the Focus Person, is a small magnifying glass icon. Click on this icon to make that relative the Focus Person (or simply double-click o...

Yes, that might make FH struggle. Maybe memory limited.

You can simplify the expression by using FindText(...) function.
{=TextIf( FindText( %FACT.DATE:XDATETYPE%, "Phrase" ) > 0, %FACT.DATE:COMPACT%, "" )}

Use the TextIf(...) function and test the following condition:
%FACT.DATE:XDATETYPE% = "Phrase"
with %FACT.DATE:COMPACT% as the next parameter.

The XDATETYPE qualifier is described in the Help for Date Formats along with COMPACT and all the other qualifiers.

Does that image display correctly in other reports such as a Media report?
Is it perhaps too large to fit on the page?
Try reducing the image size/resolution.

I assume that objective only applies to the current Generic only plugin.
Once custom Source Templates are involved that objective is impossible.

The only other option is it might be possible to adjust the wording by using a custom Language Pack to 'translate' some words in the report, but that is an advanced technique.

RM treats those items as facts, so allows all the usual subsidiary fields such as Date, Place, Note, Sort Date, Media, Citation, etc. Some are disabled by default but can be enabled and some are unlikely to be used in practice. When exported to GEDCOM those subsidiary fields are invalid and raise er...

If the field definition is known then a Query can filter on its Data Ref, e.g. %SOUR.~UL-ORIGINAL_SOURCE_FILE%

However, a general purpose search is not possible with a Query.
It would need a custom plugin to compare Source Template field definitions with Source record fields.

Coping with various templates is certainly key.
Seeing some examples will help but if you only cope with those variants the plugin may not cope with the next user customised variant. So I think the trick is to allow your plugin data set to be mapped to the template metafields by the user.

Why not start with the FH Essentials collection Civil Registration Index template?

Welcome to the FHUG. I suspect the FH direct import process is treating the Reference No attribute as a special case. By default, it has no Date or Place details so it is converted to the standard GEDCOM/FH Custom Id field. Even RootsMagic exports it to GEDCOM as a Custom Id REFN field. To refer to ...