User Profile
rbuzeta
Copper Contributor
Joined 2 years ago
User Widgets
Recent Discussions
Ms Project Online Custom Field does not rollup properly in some projects
In some projects, a task custom field that is formulated to rollup the value of [Baseline Duration] in summary tasks, shows an error when opening the project in Project Professional Desktop. The error disappears briefly when publishing and then reappears when closing and reopening the project. This does not happen in every project. It's very weird and the projects where the error is shown don't have something special, they are simple projects with baseline.Microsoft Project Professional custom fields error before publishing
I am experiencing strange behavior in Ms Project Professional. It is related to certain custom task fields. When I open a project, the fields show #ERROR (error). After making a minor change to the project, such as displaying an additional field and publishing, the error disappears. This behavior would not be a problem if, after publishing the first time, the error disappeared permanently. Unfortunately, the error persists. That is, I close the file, open it again and again the fields show an error, which only disappears (temporarily) after making a small change and publishing but reappears every time the file is opened. I tend to think it's related to a formulation that depends on two other columns with rollup. Due to the calculations I have to do I can't find an alternative solution. Has anyone seen this behavior before? Do you have a good explanation? any alternative solution?Delete projects
I just noticed that the permissions for deleting projects in Project Web App Online (PWA) are not working correctly. It's been a long time since I reviewed this option, but it seems to me that there have been changes that damaged this functionality. I have the following scenario: 1. An example user is associated with the “Project Managers” Group 2. The “Project Managers” Group has permissions on the “My Projects” Category 3. One of the permissions that the “Project Managers” Group has on the “My Projects” Category is “Delete project” 4. I have verified that there are no other “Deny” type permissions for that user in any group or category. There is no “Deny” 5. User cannot delete own projects from project center 6. User also cannot delete their own projects from PWA settings 7. Admin user and other users with admin permissions can delete any projectDesigner: Your account is in bad state. Please sign-in to this account online to address the issue.
I am trying to access a PWA using Sharepoint Designer (SPD) to configure a project workflow. This is a new Site Collection on a new Tenant. I am on the Site Collection administrator list and the Site Collection has the option to allow SPD connection enabled. The user has MFA enabled and I have generated an App Password for SPD. By following this procedure, I can connect to an old Site Collection (on an old Tenant). Consequently, I understand that SPD is installed correctly. However, I am unable to connect to the new Site Collection using SPD. I have also followed some advice on deleting cache and passwords. However, it still gives me the same error, it won't allow me to connect to PWA from SPD.Allow access to a project depending on a project field or action in Sharepoint Workflow
(1) Is there a way to allow access to a project depending on a project field? (2) Alternatively, is it possible to automatically assign a resource to a project depending on a project field? (3) Alternatively, is there any action in Sharepoint Workflow that can modify the category composition? I would like to make the definition of a projects category depend on a project field, or that resources be assigned according to a project field to get the project into a category. I understand that a project can be manually added to a Category, but I would not want to give a large number of users permission to modify the definition of a category.P4W competing with PWA
Project for the Web (P4W) and Project Web App (PWA) cover (today) very different needs. P4W has a more modern approach, technologically, but with a fairly superficial functional coverage. PWA uses legacy technologies but has hundreds of features that P4W doesn't, such as program and portfolio management, better resource management, and more progress measurement options. Sadly, Microsoft seems to be making efforts to get users to switch to P4W, without yet providing P4W with all the necessary functionality. Recently the PWA project center starts showing an icon to create new projects. New projects remain in P4W, without them being able to be managed properly from PWA, creating great confusion and problems among PWA users. Even Project Professional Desktop (part of PWA) has begun to show a decline in the quality of the application. All this would not be a problem if P4W had the depth of functionality of PWA. Do you think it is a correct strategy to start affecting PWA, to ensure a possible migration to P4W?
