* Excluding Facts/Attributes from scope of Date Warnings

[wildbill]

I discovered an old thread, 2017, but it did not answer this question. When I run the built in Fact Date Warnings report I get a long list including many custom facts which should not be within the scope of the persons life, I realise a lot of clean up from my previous program might solve this.

However I went to Fact Types and changed the Life selection to None for those Facts I wanted to exclude from the problem report but without any success.

My previous program did not problem report on custom facts or fact types like Miscellaneous, what do I need to do in Family Historian 7 to exclude them from the scope of this standard query?

[tatewise]

The first thing to recognise is that they are only warnings and not necessarily errors.
Those warnings will also arise when entering such custom facts with a Date that triggers the necessary criteria.

There are a number of potential workarounds but it would help to know which warnings you are getting.

Are all the custom facts that raise the warnings similar to your Miscellaneous example?
Do they all actually need to have a Date?
What is the purpose of the Date?

For those that do have a Date, where in the person's life span does it occur? Before birth, during life, or after death?

If no other solution is possible then you will need a custom Query derived from the standard Query that excludes your problematic custom facts, but I suspect there is a better solution.

[LornaCraig]

However I went to Fact Types and changed the Life selection to None for those Facts I wanted to exclude from the problem report but without any success.

I have just tested this with a custom fact and I found that changing the Normal Time from Life to None did have the desired effect - the fact was then omitted from the Fact Date Warnings result set. So the question is why this did not work in your case.

Is it possible that you have some custom facts with the same name but in different Fact Sets? If so, check that you have changed the timeframe for all the facts with the same name.

[wildbill]

The first thing to recognise is that they are only warnings and not necessarily errors.

Mike I realise these are warnings but I find it useful to highlight records needing possible review for errors

Is it possible that you have some custom facts with the same name but in different Fact Sets? If so, check that you have changed the timeframe for all the facts with the same name.

Lorna, I have tried again and found this to be working, perhaps it was different Fact Sets I missed first time.

Thank you both for your quick replies I see some of my entry styles were not as they should have been in my old program and need revisited, Will being one where I entered date of Administration rather than date of Will writing.

Always work to be done...

[BevSmallwood]

I am having this as well, but not because of an import problem. I ran the Fact Date Warnings report and fixed a couple of errors but what is left is people who lived to 101 and 102 and many people who married late in life.

How do I flag these as a-okay so I don't need to review them again in the future?

[tatewise]

There is no way to flag such facts to inhibit those warnings from that standard Query.

Several of the warnings are governed by the Tools > Preferences > Estimates settings.
So if you increase Maximum Life Span to say 105 years then those warnings are avoided.
Similarly, the Woman's/Man's age at marriage Maximum can be increased.

BTW: Those settings can also affect functions that estimate the date of birth and death.

Another technique is to copy the standard Query and add Rows tab filters to exclude specific Facts owned by specific people.
If you added some unique text to the Fact Note of such Facts then the Row filter need only test for that unique text in order to exclude Facts from the Result Set.

[BevSmallwood]

Mike - I'm not that confident with queries yet so I'll file this bit of advise for later on when I (hopefully) have a better grasp on it.

[tatewise]

Did changing the Tools > Preferences > Estimates settings help at all?

[BevSmallwood]

Mike - I don't even know what ages would be appropriate for marriage.

After my great grandmother died, great grandpa remarried. They were both in their 80s.

There are always outliers on the bell curve.

I think I'll have to go with a query adjustment maybe against a flag for exceptions.

[tatewise]

Bev, here is a method for adjusting the Query to exclude specific Fact Dates.

1. Run the standard Fact Date Warnings query
2. Use the cog Query Menu to Save As Custom Query... with a name such as Fact Date Warnings with Filter
3. On the Rows filter tab Add Exclude if... %FACT.NOTE2[1]% contains Fact Date OK and tick Match case

That will exclude any Fact whose Note contains Fact Date OK (or whatever unique text you prefer).
That text can be enclosed in [[ privacy ]] brackets to exclude it from Diagrams and Reports.

This new custom Query will appear in the Query > Facts and Events menu just like the original.

If you don't like the concept of unique text in the Note box then there are other options possible.
They typically involve setting a field via the All tab but it is not difficult.
You could even decide that if there is Source Citation then that is proof enough the Date is OK.

[BevSmallwood]

Mike - copied to create new query but there is already an exclude statement on Rows:

Exclude if %FACT._FLGS.__REJECTED% is set.

What is it referring to? Is there already a flag created or do I need to create one called REJECTED?

[BevSmallwood]

I followed your instructions and it works fine.

I see that the rejected flag is part of the Private-Preferred-Rejected-Tentative set. It would be nice if "confirmed" could be added to that set.