Hi all,
we have a need to be able to backdate posts. my business office wants to limit backdating to the beginning of the current month only. my idea is to run a nightly job to update the POSTING MAX BACKDATE DAYS setting to the appropriate number of days to only allow backdating to the beginning of the month. does anyone have any better ideas solutions? a setting I'm missing? or any reasons not to do this?
Hi Mendy,
I suppose I would be curious as to the business purpose behind it besides the obvious "this way we now cannot possibly screw up last month's data" approach. For our own organization, our business practice is to post the previous day's activity every day, and the only time we get a day or two behind is when no one from the Box Office is in on Sunday (or the rare closed Saturday), but then those are all done the next business day. We just set ours to 30 and leave it at that.
In terms of the procedure, I suppose that would work, and it sounds pretty straightforward, though you might have to be careful about posting on the 1st of the month, as usually you would be posting the previous day's web activity, and that procedure might have already updated it to be the first of the new "current" month (similarly for weekends as described above). Alternatively, you could just run the procedure once monthly, changing the date each time, since you can also just put a date in rather than a number of days.
Anyway, it sounds like your idea should work if you really need it to do that. I cannot think of any reason why you should NOT do that other than the fact that updating T_DEFAULTS regularly sounds like an unusual set-up.
John
my business office likes to close and seal the month. You raise a number of good points. i might need to set it at a minimum of 3,4,5 days instead of 1. i think I'll add a report that will take number of days or date so the business office can manipulate the value one off without needing IT.