2019.R2(S1):RulesExport-Export Start Date is 1-1-0001

This is probably the known DIT issue, but I'm tracking with a ticket so that I can complete and not hold up testing.

The export file has a start date of 1-1-0001.  I think Caner has listed in details the options:

"During DIT I have found an issue about the export:

in case the export runs from server manager it inserts data to tbauditexport table. Lets say for the first time we ran by last week on 01/01/2019. That would export all the rules have "ApplyDates" before that day. That is fine. 

Also assume that we re exporting from Mobile or MMS UI (not from Server manager) the rules before 01/01/2019 then that would work fine too. 

But if we re-export from UI on 01/03/2019  which is after 01/01/2019 (last time exported from server manager) then this will also insert data to tbauditExport table. if we re run export from server manager today then it will find 01/03/2019 as the last exported date. And it will include the rules are being applied starting from 01/03 up to today. We will be missing 01/02/2019 in the export file. 

Unfortunately there is no indication when the export runs that if the export request coming from either UI or Server manager for me to distinguish. 

 The question is shall we be able to 

One solution in my mind is that dont export anything from UI if the selected re-export dateis after the last exported date.

(Because we haven't exported those days yet should we be able to re-export the days that we havent exported yet?) . 

I am not sure if that would be ok. Otherwise I will have to find another way to solve this problem. 

 I would like to know what you guys think? "