Family Historian User Group

Yes, if the separator is a comma, then the TextPart(...) function works similarly to the Section(...) function.

TextPart(...) also has extra features for tidying and arranging the comma-separated parts.

Ok, you are very close. I think the following may be what you want but there are some caveats. =Text( %SOUR.~NM-Principal:SURNAME_FIRST% . ": " . Section( %SOUR%, 1, "," ) . " " . %SOUR.~DT-Date:YEAR% ) %SOUR.~NM-Principal:SURNAME_FIRST% will display the Surname, a comm...

Please confirm whether you would be happy to simply reformat the Source Record Title or not.

To add a Record Id to the final Result Set ... About line 95 add a table variable to hold the Record Id: tblRecord = {} tblRec_Id = {} About line 115 save the Record Id in the table: table.insert(tblRecord,pi:Clone()) table.insert(tblRec_Id,fhGetRecordId(pi)) About line 128 display Record Id in the ...

Yes, {individual} experienced {label} ... is the default Sentence Template for a new custom Event or one without a definition.

Just to be clear, the extra symbols and diacritic letters supported by ANSI coding are only: € ‚ ƒ „ … † ‡ ˆ ‰ ‹ Æ æ Œ œ ‘ ’ “ ” • – — ™ › ¡ ¢ £ ¤ ¥ ¦ § ¨ © ª « ¬ ­ ® ¯ ° ± ² ³ ´ µ ¶ · ¸ ¹ º » ¼ ½ ¾ ¿ × ÷ Þ þ ß Ð ð nbsp À à Á á  â à ã Ä ä Å å Ç ç È è É é Ê ê Ë ë Ì ì Í í Î î Ï ï Ñ ñ Ò ò Ó ó Ô ô Õ õ ...

Ok, the following two changes should be sufficient, unless your Surnames use foreign language characters. Near line number 16 add three lines after iup.SetGlobal("CUSTOMQUITMESSAGE","YES") to cope with UTF-8 require("iuplua"); iup.SetGlobal("CUSTOMQUITMESSAGE"...

John, you can edit the plugin yourself to make any necessary changes.
One of us could advise what changes to make once you are familiar with the editing process.

Alternatively, you must wait until Jane notices this thread and updates the plugin in the Plugin Store.

FYI: The plugin is using iup.GetText(...) which displays a modal dialog to edit multiline text. The idea is that the user reviews and corrects each surname listed. However, in Lua the default maxsize is 10240 characters, so I believe the dialog is being truncated. So it is currently not possible to ...

I have moved this from the Diagrams & Charts forum to the Reports, Books & Websites forum which is more appropriate. The explanation for that narrative sentence is that the Fact Type definition for the General Event is missing or needs refining. Use Tools > Fact Types... and then if possible...

The 'safe' plugin script solution is to cater for every :match(...) operation possibly returning nil . Don't assume that such a match will always be successful, i.e. use defensive programming techniques. Similar techniques should be applied to all other operations to avoid unexpected failures. In th...

Yes, that is the same cause for the error.
The NSFX = POLLARD/ which is the trailing part of the NAME field and includes the slash /
So when the 'suffix' POLLARD/ is removed from Ella Loretta /POLLARD/ it leaves Ella Loretta / which does not contain two slashes and that causes the fault.

I discovered that fault arises under the following (unusual) conditions:
Name (INDI.NAME): Ian Steve /Munro/ Junior
Name Suffix (INDI.NAME.NSFX): Munro/ Junior
i.e. The Named Suffix field holds the trailing section of the Name field including a slash /

Yes, that is a good find from 2+ years ago!

Yes, I think that is the only manual method available and must be applied one Citation at a time.

To make a large number of changes in bulk will require a custom plugin to be written.

I think the following is the explanation but without seeing the diagram it is difficult to be certain. When cousins marry they bridge across generations so their relatives have two relationships to the other members of the family tree. The duplications illustrate where such people fit into their two...

You could create a copy of your master Project and delete the maternal line of ancestors.
Then the report will only include the paternal line.

The choice is yours. In Internet > Internet Data Matches... the Settings have the following options for both FMP and MH: 1) Enabled for all Projects except those with 3) selected 2) Disabled for all Projects 3) Disable for this project only The hints are only active for the people shown in the curre...

Yes, you must use Condition > Expressions instead of Condition > Record Flag
Use the << Insert Data Ref... button to add Individual > Flags one at a time, e.g. %INDI._FLGS.__LIVING%
Then the order of the Conditions determines the order of the icons.

That will refer to whatever happens to be the 1st Templated metafield in each Citation.

To refer to them by name see the Help for Understanding Data References and scroll down to Data References And Metafields as I explained earlier.

They had to be Templated Sources because Citation Detail and Reference are not Generic fields.
BTW: Once you create a Query it is immediately saved. You would have to specifically delete it.
You can use any existing Query to interrogate the Fields DRA without affecting the Query.

Unfortunately, the Query > Columns tab > Fields pane does not support Templated Named Metafields. Please refer to the Help for Understanding Data References and scroll down to Data References And Metafields . There it explains the data reference structure for metafields. e.g. %FACT.SOUR[1].~TX-REFER...

%FAMS.MARR[1].PLAC>STAN% is almost a perfectly correct Data Reference for the Standardized field. %CUR~FAMS>MARR.PLAC>STAN% is what you should use for the Marriage Standardized place. However, it is not allowed in the position you have used in a =FactText(...) function, so is ignored. The =FactText...

It might help if you could post screenshots of the Marriage Certificate and 1881 Census. See the FHUG Knowledge Base > Forum Usage under Attachments and Taking Screenshots for how to do that. Are you looking in Census records for a William about the right age with father John and mother Jane? Try th...

Welcome to the FHUG. It is quite common for entries on Census Returns to be erroneous and inconsistent. Unlike BMD Certificates that are completed near the date & place of the event, Census birth details rely on the person remembering and the enumerator hearing & recording the details correc...