Yes a custom fact would be appropriate.
My perspective: Many people will disagree with me on the following points and they have the right to their opinion, however I come from a position that, a) newbies should learn a little about the bigger picture beyond FTMs "box". b) Interchange of Genealogy information should be made via GEDCOM and the GEDCOM standard should be followed even if you think it is flawed (it has a few). c) Use tools correctly don't use a screwdriver for a hammer.
A couple of things to learn about custom facts from the GEDCOM perspective:
1) The "Fact Label" value becomes the "name" of the fact, in a well formed GEDCOM this is the "TYPE" tag. Similar to a primary tag of BIRTh, DEATh etc. So care should be taken to define this value so that it has the ability to be reused. For example GEDCOM does not have a "Military" tag. FTM creates a "Military Service" tag using a _MILT value. This is not incorrect just not the best choice. I could write a paper on why this is not the best choice.
2) The entered description (after adding the new fact) is used to better/further define what the fact is about.
So for example in the case of _MILT vs a true custom fact (the better way).
For families that have lots of military service and events in their family creating a "Military" custom tag is better than using the "Military Service" fact in FTM because it is more versital.
You could have a Military tag with a description of "Service", or "Honors", or engagements (i.e. "Battle of Gettysburg", "Battle of Bull Run") where "a fact of "Military Service" only implies serve dates.
If your family was politically inclined a custom tag of "Government Offices" would be valuable because the description could contain the various positions held, (i.e. State Rep, Mayor, Alderman, Appointed Offices).
Some thoughts on the custom fact: You could create a custom fact like "Legal Action" or "Criminal Action" with a description of "Murder" or something else. Don't over think this but put a little though into how the custom tag could be reused by other individual events.
I create one "fact" called "Crew". Where the description is the name of the ship. Almost every male member of one line my family in the 1700's and 1800's went to sea and in many cases I have information about the ships the were on. This allows me to list these ships and dates where the FACT.TYPE is "crew", and the description is position and ship name.
My perspective: Many people will disagree with me on the following points and they have the right to their opinion, however I come from a position that, a) newbies should learn a little about the bigger picture beyond FTMs "box". b) Interchange of Genealogy information should be made via GEDCOM and the GEDCOM standard should be followed even if you think it is flawed (it has a few). c) Use tools correctly don't use a screwdriver for a hammer.
A couple of things to learn about custom facts from the GEDCOM perspective:
1) The "Fact Label" value becomes the "name" of the fact, in a well formed GEDCOM this is the "TYPE" tag. Similar to a primary tag of BIRTh, DEATh etc. So care should be taken to define this value so that it has the ability to be reused. For example GEDCOM does not have a "Military" tag. FTM creates a "Military Service" tag using a _MILT value. This is not incorrect just not the best choice. I could write a paper on why this is not the best choice.
2) The entered description (after adding the new fact) is used to better/further define what the fact is about.
So for example in the case of _MILT vs a true custom fact (the better way).
For families that have lots of military service and events in their family creating a "Military" custom tag is better than using the "Military Service" fact in FTM because it is more versital.
You could have a Military tag with a description of "Service", or "Honors", or engagements (i.e. "Battle of Gettysburg", "Battle of Bull Run") where "a fact of "Military Service" only implies serve dates.
If your family was politically inclined a custom tag of "Government Offices" would be valuable because the description could contain the various positions held, (i.e. State Rep, Mayor, Alderman, Appointed Offices).
Some thoughts on the custom fact: You could create a custom fact like "Legal Action" or "Criminal Action" with a description of "Murder" or something else. Don't over think this but put a little though into how the custom tag could be reused by other individual events.
I create one "fact" called "Crew". Where the description is the name of the ship. Almost every male member of one line my family in the 1700's and 1800's went to sea and in many cases I have information about the ships the were on. This allows me to list these ships and dates where the FACT.TYPE is "crew", and the description is position and ship name.