* Error when running 'Change Any Fact Tag'

[cwhermann]

I am trying to change a custom fact/attribute called Will Proved imported from RM8 to a standard fact/event called Will using the Change Any Fact Tag plugin. The Change "Source Tag Name' into the "Target Tag Name" button stays grayed out and I cannot complete the change. See image below.

I ran the plugin to make sure all installed plugins were up to date. I read through the help and examples but cannot determine what I am doing wrong.

Change Fact Type.png (22.47 KiB) Viewed 2032 times

[tatewise]

Yes Curtis, I can repeat those symptoms. Sorry!
It is specifically related to the RootsMagic Import Fact Set local to the current Project, and I will try and fix that ASAP.
However, if you alter it to being a System-wide Fact Set the problem does not arise.
To do that use Tools > Fact Types..., click Fact Sets... and choose RootsMagic Import, then click Settings... and untick Current project only.
After using the Plugin you can alter it back to Current Project only if you wish.

[LornaCraig]

As an aside, you might want to consider changing the custom Will Proved fact to a standard Probate fact rather than a standard Will fact. You will see from the sentence templates for these facts that the Will fact is intended to be used for when the will was made, and has a normal time frame of Life. The Probate fact is for when the will was proved, and has a normal time frame of Post-Death.

[cwhermann]

Mike,
I will change them to system wide fact and give it a try.

Lorna
I agree, in general will proven should be a probate fact, but in this instance it should be when the will was written. This is a “one occurrence” change which easily could have been done manually and I was using it to gain experience with the plug-in before attempting to change RM8 custom census facts to the standard FH census fact.

Thank you both for your help and guidance.

[tatewise]

While investigating the problem I discovered that if you change the Source Tag Set: to something else and then back to RootsMagic Import (project) everything works OK.

[Mark1834]

I tested as well, in case it has any implications for the Change Specific Fact Tag plugin, using a test RM8 database with one individual and one custom fact.

Change Specific Fact Tag ran normally, but I did have a couple of observations -

Change Any Fact Tag gave the symptoms that Curtis described irrespective of whether the RM Import Fact Set was kept at the project level or promoted to system. However, if I added another standard fact to the individual, the plugin appeared to work normally! Delete the standard fact, and it misbehaves again.

There may be an issue with FH not correctly handling having both project and system level RootsMagic Import Fact Sets. I'm getting inconsistent results with how the various sets are recorded in the GroupIndex.fhdata files (which may be either empty or referring to a non-existent Fact Set). I need to do some more testing, but there may be an FH bug here as well...

Added in edit: What appears to be happening is that if a Fact Set is moved between system and project, the index entry in the old location is not deleted. In addition, if all the project level Fact Sets are deleted, the entries are deleted from the index file, but the empty file is not deleted. Both of these confuse the Change Specific Fact Tag plugin, as I had not considered the possibility that the index file could be empty or refer to non-existent files. They may not explain Curtis’s observation, but it does feel like a bug that needs reporting.

[tatewise]

I have found the primary cause of the Change Any Fact Tag plugin symptoms, which are due to a bug that is triggered by the local Project Fact Set(s) being higher precedence than the system Fact Set(s).
The fix seems to work on my system, but the issues raised by Mark need investigation.
There are some other changes needed to bring the plugin up to date and cater for files with UTF-8 paths.
I am busy with DIY jobs just now, so it will take a while to complete all the changes and testing...

[cwhermann]

While investigating the problem I discovered that if you change the Source Tag Set: to something else and then back to RootsMagic Import (project) everything works OK.

By adding this step in the process I have been able to change fact tags. So far, I have only changed facts associated with specific individuals. Hopefully this week end I will get an opportunity to use the plugin to change a fact across the entire database.

Thanks again for the great assistance from the group.

[Mark1834]

The Change Specific Fact Tag plugin has now been updated in the Store to accommodate the inconsistencies and variability in Fact Set definition that have been observed recently.

Specifically, the RootsMagic Import Fact Set is structured differently to other sets, and Fact Set index files can list sets in arbitrary order and/or include non-existent sets if sets are moved between System and Project level.

[tatewise]

Sorry this has taken so long, but I've at last fixed the Project Fact Set bug and incorporated some other necessary changes.

See attached Change Any Fact Tag plugin Version 3.6.1 Date 08 Nov 2022.

Please let me know of any problems before it is published in the Plugin Store. It should work on any FH version.

The new features include:

• Fixed bug reported here where local Project Fact Set(s) have higher precedence than system Fact Set(s).
• Caters for multiple local Project Fact Sets.
• Copes with UTF-8 file paths for the Project and Fact Set files.
• Handles any Fact definitions with a UTF-8 Label.

[tatewise]

Following some feedback and further testing here is a revised version.

See attached Change Any Fact Tag plugin Version 3.6.3 Date 10 Nov 2022.

Please let me know of any problems before it is published in the Plugin Store.
It should now work on any FH version, whereas the previous Version 3.6.1 did not.

In addition to the features mentioned in the last post, the new features include:

1. The Source Tag Set and Target Tag Set now split each Fact Set into two subsets for Events and Attributes.
   This allows facts (especially imported ones) to have the same Name/Label for both an Event and an Attribute.
   That allows such Events to be changed to the synonymous Attribute more easily.
   It also should make the selection of facts simpler by shorting the Fact Name drop lists
2. The QUIT Plugin and UNDO Updates button now simply closes the plugin if there were no changes.
   Otherwise, it advises that the Edit > Undo Plugin Updates command should be used.

[Mark1834]

Looks good, thanks. I definitely find it easier to use with Events and Attributes separated, and the close message is a lot clearer as well. Having that separation in common between the two complementary plugins (Any Fact and Specific Fact) should make life easier for the general user as well.

[cwhermann]

Worked great - changed a couple of RM attributes to a different RM attribute with no problems.

[tatewise]

Change Any Fact Tag plugin Version 3.7 Date 16 Nov 2022 is now in the Plugin Store.

The prototype versions attached below will soon be deleted.