Enterprise resource duplicate

[BudOlly]

Hello,

I've been testing PWA fairly rigorously, and I've come across an
inconsistency in the enterprise resource pool. I created a resource named
"Test", and tied it to an active directory user account, so I can use this
account to test out permissions and so forth.

I've been writing code to process queries on the DB's, and I've noticed that
in the dbo.MSP_TIMESHEETS table there are two rows, each with the same
timesheet period, and same resource name, but different RES_UIDs.

So, it seems that I have two resources with the same name, but different
UIDs. However, this discrepancy does not exist is the dbo.MSP_RESOURCES
table, so I'm assuming that somehow during deleting and recreating the
timesheets, the DB became out of sync. At this point, the resource does not
even show up in the server settings under "Delete Enterprise Objects", but I
can see it by looking directly in the SQL Database in the dbo.MSP_RESOURCES
table.

Does this make sense, and if so, could somebody please explain to me how
this happens, so I can avoid it in our production environment. Or, if this
is an unavoidable downfall of PWA, is there a recommended 'Best Practice' for
keeping the DB's synchronized?

Is it safe to delete that row from the MSP_TIMESHEETS table? With the
orphaned record, my query results are returning the wrong number of
timesheets for a given period.

 

[Gary Chefetz]

BudOlly:

In production, you are not going to make a practice of deleting resources as
this disassociates important historic records. The only time you would ever
delete a resource is if you created one in error and the resource was never
used, or possibly if you were doing some very deep housecleaning after some
years of use. So, consider this a pitfall, not a downfall, of playing around
with the system in test mode. If you follow best practices, this should
never become a production issue. However, it sounds like you're on a strong
learning path and your curiosity will lead you to mastering the system.