4/1/2023 0 Comments Ms project server 2013![]() * ( MSP_EpmAssignment_UserView.AssignmentWork/ MSP_EpmProject_UserView.ProjectWork ) When MSP_EpmAssignment_UserView.AssignmentWork = 0 THEN 0 One step further, we can do the same using task assignment data, here’s what that looks like using the assignment work: ORDER BY MSP_EpmProject_UserView.ProjectName, MSP_EpmTask_UserView.TaskIndex, MSP_EpmTask_UserView.TaskName ![]() ![]() ON MSP_EpmProject_UserView.ProjectUID = MSP_EpmTask_UserView.ProjectUID * ( MSP_EpmTask_UserView.TaskRegularWork/ MSP_EpmProject_UserView.ProjectWork )įROM dbo.MSP_EpmProject_UserView INNER JOIN dbo.MSP_EpmTask_UserView When MSP_EpmProject_UserView.ProjectWork = 0 THEN 0 When MSP_EpmTask_UserView.TaskRegularWork = 0 THEN 0 The next problem is if merging task and project tables, project values would roll up incorrectly, however such numeric fields can be pro-rated to the project work, as long as we avoid divide-by-zero errors, here’s how, referencing a custom field called “Budgeted Costs” note how its value is proportionate to the task work: Where TaskIsSummary=0 and TaskIsExternal = 0 The next source for double-counting are external tasks those exposed through cross-linking tasks in separate projects. The solution is to exclude them on the join, adding this condition: ![]() The first challenge is avoiding double-counting from summary tasks. ![]() If joining Task and Project data, there’s a challenge of rollups. The SQL can be embedded in an ODC, or can be used within PowerPivot. It is easy to navigate the database schema in MS-Project Server to generate reports. eDiscovery and Records Management SolutionsĬustom SQL Reporting in MS-Project Server 2013. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |