F
Frederick
Good day,
We need to massively "hide" tasks from resource's PWA timesheets; the
existing user executed function is tedious (1 task at a time with 3 pop-ups).
Therefore, we are in the process of programming an application which would
allow us to massively hide tasks for given projects/resources in their
timesheets.
We are planning on using the stored proc
"MSP_WEB_SP_QRY_RemoveFromTasksPage" on the MSP_WEB_ASSIGNMENTS table
combined with some parameters like resource name & project plan names.
Something akin to this:
CREATE PROCEDURE dbo.MSP_WEB_SP_QRY_RemoveFromTasksPage
@p0 NTEXT,
@p1 INT
AS
Update MSP_WEB_ASSIGNMENTS set WASSN_REMOVED_BY_RESOURCE=1 where WASSN_ID in
(select TokenVal from dbo.MSP_WEB_FN_ConvertListToTable(@p0)) and WRES_ID=@p1
RETURN(0)
Has anyone ever tried this? Can we trust the stored proc to behave properly
eventhough it seems designed for "single use"?
Thanks a bunch!
We need to massively "hide" tasks from resource's PWA timesheets; the
existing user executed function is tedious (1 task at a time with 3 pop-ups).
Therefore, we are in the process of programming an application which would
allow us to massively hide tasks for given projects/resources in their
timesheets.
We are planning on using the stored proc
"MSP_WEB_SP_QRY_RemoveFromTasksPage" on the MSP_WEB_ASSIGNMENTS table
combined with some parameters like resource name & project plan names.
Something akin to this:
CREATE PROCEDURE dbo.MSP_WEB_SP_QRY_RemoveFromTasksPage
@p0 NTEXT,
@p1 INT
AS
Update MSP_WEB_ASSIGNMENTS set WASSN_REMOVED_BY_RESOURCE=1 where WASSN_ID in
(select TokenVal from dbo.MSP_WEB_FN_ConvertListToTable(@p0)) and WRES_ID=@p1
RETURN(0)
Has anyone ever tried this? Can we trust the stored proc to behave properly
eventhough it seems designed for "single use"?
Thanks a bunch!