B
BudOlly
Hello all you Project Gurus out there... Thank your for taking the time to
read my post, this community is always so helpful!...
I just have a question about manually cleaning up rogue database entries.
What I mean by 'rogue' may be slightly off from the traditional definition...
I've noticed if a user creates a timesheet line and deletes it, data analysis
never loses that timesheet line. DA does not report the line directly, but
if you use the checkboxes from the "Task" field's drop-down list, all the
previously deleted task names still show up. Since we are using these
check-boxes as a way to differentiate 'unverified' tasks, it would be a lot
less 'tangled' if we could do away with any task names that our users have
deleted, and renamed for instance.
I have found the entries in a table called 'dbo.MSP_TimesheetTask' in PWAs
reporting database, and am experimenting with simply deleting the records
from that table. I realize this is considered bad practice, and to be honest
I don't know if those entries are tied to any other tables in the DB.
So, if there is a better way to handle this, or if I would be better off
leaving those entries alone, I am all ears for advice!
read my post, this community is always so helpful!...
I just have a question about manually cleaning up rogue database entries.
What I mean by 'rogue' may be slightly off from the traditional definition...
I've noticed if a user creates a timesheet line and deletes it, data analysis
never loses that timesheet line. DA does not report the line directly, but
if you use the checkboxes from the "Task" field's drop-down list, all the
previously deleted task names still show up. Since we are using these
check-boxes as a way to differentiate 'unverified' tasks, it would be a lot
less 'tangled' if we could do away with any task names that our users have
deleted, and renamed for instance.
I have found the entries in a table called 'dbo.MSP_TimesheetTask' in PWAs
reporting database, and am experimenting with simply deleting the records
from that table. I realize this is considered bad practice, and to be honest
I don't know if those entries are tied to any other tables in the DB.
So, if there is a better way to handle this, or if I would be better off
leaving those entries alone, I am all ears for advice!