* Lookup Missing Census Facts

[mikegscoles]

That is the answer. Thanks for all your efforts.

Would it be possible to check the size of the tree and issue a warning if it is larger than 1000?

I did not think to read the Help & Advice page or refer to the KB as I have used the plugin many times in the past and not picked up any issues.

Thanks again for your help.

Mike

[tatewise]

It is not the size of the Project tree that matters, but the number of Individual records selected to be searched by the Plugin, which can change from one run to the next.
The Plugin used to curtail the Facts search regardless of number of records, but the problem you encountered happened quite often, so it was suggested to change to the current scheme.

The Plugin could warn when the Facts search is being curtailed and Date order is important, but that becomes an annoying nag when the Plugin is run repetitively. So it would need some kind of 'one-shot' mechanism such that the warning is only produced say once per day. However, it should be second nature for users to re-order Facts after a series of updates, because there are many side-effects in Diagrams, Reports, etc, if not in Date order.

[tatewise]

I have revisited this scenario.
Originally, I thought of adding an option to the user dialogue to ask if the Facts were all sorted, which would also act as a reminder to do so.
But then I went one better and decided to sort the Facts in the Plugin, which does not cost much if they are already sorted.
Expect to see this refinement in the next version.

See new Plugin in Lookup Missing Census Facts (13629).

[tatewise]

Lookup Missing Census Facts Version 4.0 Date 15 Apr 2016 is now in the Plugin Store and fixes the updated Facts out-of-sequence problem by sorting Facts internally.