Hello all,
Could someone please tell me why a custom event from FS doesn’t find the same mapping in RM11?
before:
added as a new fact:
I think it’s because it’s a custom field with a user-defined tag, and therefore it can’t be assigned a keyword in RM.
What’s the best way to handle this?
my first thought would be to add to RM first then push to FS – not sure. It might be due to the two (custom) facts have diff layouts – just a guess
Thanks, I try to collect some facts, because this happens not in all cases. But it happened in the most of the addition.
The second fact type BAPTISM is the same but without WITNESS (last line/entry). So I will try it out and reply.
Case I (with WITNESS)
I have added the fact BATISM before and get the option to update the fact. So it works!
case II
Now I know the reason, but what can I do to have the correct fact type created?
Are you referring to the differing presentation of the word ‘Baptism’ within the Other Information column as being bolded versus italicized?
I always assumed that the presentation( in your images) was meant to indicate “recognition” by RootsMagic that a Custom fact with the same fact name as a reserved Fact Type name had been detected and thusly …warranted an additional separate column entry below (then bolded after marked for transfer)… while the reserved fact name was still displayed above it (in italics) to represent the specific Baptism fact of the GEDCOM standard. But, I was only ever assuming.
Again, I always “assumed” this was where LDS ordinances come into play (as the FamilySearch website events do not offer Baptism as an + Add Event selection rather than the Custom event route) because baptism (around 8 years old) is a separation of concerns via “internal” church system recording methods and confirmations/sealings.
It runs well at the fact type MARRIAGE, but BAPTISM not - I would say rare.
I would like to know if I should change the Fact Type BAPTISM and add “witness” or if I can combine both fact types.
The presence of two identical fact types—one with a “Witness” role and one without—usually occurs during a GEDCOM import or when merging data from different sources.
Baptism with “Witness” role: This is a shared event type. It allows you to link other people (like godparents or witnesses) to a single baptism event. The software uses the “Witness” role to automatically generate sentences for those individuals in their own timelines.
Baptism without “Witness” role: This is a basic event type. It only records the fact for the primary person and does not have the pre-configured structure to “share” the event with others easily.
By merging these into the version that includes the “Witness” role, you have:
Consolidated your data: All baptism entries are now under one category.
Increased functionality: You can now add godparents to any baptism record using the “Shared Event” feature without losing any existing dates or places.
Cleaned your Reports: Your narrative reports and lists will now be consistent, as RM11 no longer has to distinguish between two different “Baptism” definitions.
So I updated the fact type baptism II (without witness role) at all persons to baptism I. Then I delete the batism II fact type and it runs well. I used this
