Dear Community,
Has anyone else noticed anything strange when it comes to allocation details? Last year, one of our users reported that their name appeared in an allocation they couldn’t have created, they had no access to the resource or the project. After some analysis, we found out that the user wasn’t even logged into the system that day!
We immediately opened a case with Customer Care, but so far, despite many attempts to prove that the issue is not on our side, we still don’t have a resolution and the data has been unreliable for more than a year!
We even built a dataset from the allocation table to check for discrepancies between the created_by, requested_by, and approved_by columns. It turns out that in the requested_by column, there are cases where a person without the proper profile somehow managed to create a request for an allocation. They simply don’t have the right grants or role feature to perform the action.
Customer Care suggested this might be related to copying project plans but we’ve ruled that out for the specific cases we’ve analysed. We also excluded user error since in many cases those users weren’t even logged into the system on that day.
Additionally, we’ve noticed anomalies where the creation_date is later than the requested_date which obviously shouldn’t be possible.
I can share the sql query we’re using so you can check if you see the same issue in your own database. At this point, the only thing we can really do is see if other customers are experiencing the same problem, maybe then Planview will finally take it seriously.
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
SELECT
alloc.planning_code,
alloc.resource_code,
res.description AS resource_name,
alloc.user_name,
creator.full_name AS created_by,
crole.description AS creator_role,
alloc.date_created,
alloc.request_date,
alloc.requester_name,
requester.full_name AS requested_by,
role.description AS role_name,
alloc.approve_date,
alloc.approver_name,
approver.full_name AS approved_by
FROM ip.allocation AS alloc
JOIN ip_user AS creator
ON alloc.user_name = creator.user_name
JOIN ip.structure AS crole
ON creator.role_code = crole.structure_code
JOIN ip_user AS requester
ON alloc.requester_name = requester.user_name
JOIN ip.structure AS res
ON alloc.resource_code = res.structure_code
JOIN ip.structure AS role
ON requester.role_code = role.structure_code
LEFT JOIN ip_user AS approver
ON alloc.approver_name = approver.user_name
WHERE alloc.requester_name <> alloc.user_name
ORDER BY alloc.date_created DESC;
