Finance | Project Operations, Human Resources, ...

Couldn't Assign Resources to the tasks in Project Operations

(1) Share

Report

Posted on by jliang55

Hi Community,

[Deployment type: Project Operations for resource/non-stocked based scenarios]

This is in one of our UAT environments, I come across this "Couldn't assign resource, please try again" error when assigning one of the Resources to a task. My user account has "system admin" security role. I can assign other Resources to the same project or other projects, or add the Resource to the Team tab under a project, but I just cannot assign this Resource to any Task.

I have this user to also give a try using her own account, which has most of the Project related security roles except the "Project Owner" role. But same happens. She could assign other Resource to tasks but couldn't assign her own Resource to any Task in any Project.

I've checked and compared the user's Dynamics license, she has the D365 CE Plan, which is same and standard for our CE/PO users. A ticket has been submitted to MS Support with those Correlation IDs and timestamps when we reproduced the issue, but so far there isn't a fix yet other than suggestions to check license and security roles.

I've also tried other postings from the forum and the troubleshooting section on the product user doc, such as checking the web browser settings and the Role from FO, things seem right.

I understand behind the scene it's the "Project for the Web" service running, but I am not quite familiar with "Project for the web" to be honest. So I wonder if I am still missing any setup for this user?

Has anyone come across the same or had any suggestion, please advise.

Thank you,

Jimmy

All responses (18)

Answers (0)

Brittany W 7 on at

Like (0)

Report

RE: Couldn't Assign Resources to the tasks in Project Operations

Did you hear anything more from the Product team? We are experiencing this issue but we use a generic resource for all of our task estimating. The generic resource also seems to have capacity set and so far I have not been able to turn it off. It would seem that you should be able to just toggle the capacity off but it does not seem to stick when I try.
JHarvey 108 on at

Like (0)

Report

RE: Couldn't Assign Resources to the tasks in Project Operations

We had the same problem and resolved it via MS Support...

Go to RESOURCES, select the resource that is failing... go to WORK HOURS and click on the working hours schedule in the calendar. Chose EDIT, then "this and all following events"... in the next screen, make sure that CAPACITY is set to ONE. This is a bug that MS acknowledged...

MS:

Additionally, we confirmed that setting the capacity of the affected resources to 1 allows you to assign them correctly, please continue to utilize this while I review further with our product group why the lower capacity works when a higher capacity (such as 3) returns the error.

Quoting the official documentation on capacity:

"Capacity is the number of times the resource can be booked during that specific work hour. For example, setting the capacity to 5 means that when booking a resource with the schedule assistant, the resource will show as available and can be overbooked up to the capacity limit (in this case, five times). It's set to 1 by default. If this setting is set to 0, the resource will never be shown as available in a resource search."
samwillm 142 on at

Like (0)

Report

RE: Couldn't Assign Resources to the tasks in Project Operations

If you are unable to assign resources to tasks in Project Operations, there are several potential reasons why this might be happening. Here are some troubleshooting steps you can take:

Check your security roles: Make sure that your security role grants you permission to assign resources to tasks. If you do not have the necessary permissions, you will not be able to make assignments.

Check the project settings: Ensure that the project settings are configured correctly to allow resource assignments. To do this, go to the project settings and check that the "Schedule" section is set to "Automatically schedule" and that the "Allow resource selection for task assignments" option is enabled.

Check the resource pool: Verify that the resources you are trying to assign to the tasks are available in the resource pool. If they are not, you will need to add them to the resource pool before you can assign them to tasks.

Check resource availability: Ensure that the resources you are trying to assign to the tasks are available during the scheduled task duration. If they are not available, you will need to adjust the task schedule or assign a different resource.

Check the task type: Verify that the task type is set to "Fixed Duration" or "Fixed Units" as these are the only types of tasks that allow resource assignments. Tasks set to "Fixed Work" do not allow resource assignments.

If none of the above steps resolve the issue, you may need to contact Microsoft Dynamics 365 Project operations support for further assistance.
onciprian28 5 on at

Like (0)

Report

RE: Couldn't Assign Resources to the tasks in Project Operations

Hi, I have the same problem. I assign the default template calendar to the user and the error was gone. If I set the Calendar to a costume one the error appears.
jliang55 55 on at

Like (0)

Report

RE: Couldn't Assign Resources to the tasks in Project Operations

Hi Spalanidurai,

We have been setting up a couple of PO environments for evaluation and testing purposes in the past few months. But we just started with the latest version available at the time when we created a new instance. I don't think we've performed update yet but I need to double check. This issue came up in two environments if I recall correctly, but only in this particular environment we tired everything without luck.

Regarding the Scheduling API, Antti Pajunen has this great post by using Power Automate and project template. Not sure if it will help with the other issue you came across.

Dynamics 365 Project Operations: Using Schedule APIs with Power Automate and custom project templates (daytodaydynamics365.com)

Cheers,

Jimmy
Spalanidurai 45 on at

Like (0)

Report

RE: Couldn't Assign Resources to the tasks in Project Operations

I have adjusted start date, Due date, Duration of the specific task which could not resolve user. I did not change Project start date, due date in Project summary.

If you have already tried adjusting Task date, Please ignore , Otherwise give a try and let me know.

What PO version installed in the tenant? We are facing some issues with Scheduling API (Copy project, Operationset) after recent Project Operation update. We opened ticket and working with Microsoft. Is this issue existed earlier version or you started experiencing after PO product update.
jliang55 55 on at

Like (0)

Report

RE: Couldn't Assign Resources to the tasks in Project Operations

Hi Gert,

Thank you for getting back to me and everyone else facing the same.

The error came up in two projects for the same Resource on my end - one project is with a quote and a project contract; and the other project is simulating for internal use project so no quote or project contract related.

Regarding the replies from MS Support, I got similar feedback from them asking me to check categories, posting profile and etc. from FO's end.

We have started up a new environment and didn't come across the same issue, yet. So, definitely, we want to know what the root cause could be.

Cheers,

Jimmy
Community Member Microsoft Employee on at

Like (1)

Report

RE: Couldn't Assign Resources to the tasks in Project Operations

Hi all, we have made progress. A couple of things were tested.

-Create a project with no quote or contract. This worked and we could add resources to tasks and it replicated to F&O.

-Created a project with only a quote. This worked and we could add resources to tasks and it replicated to F&O.

-Created a project with a quote and contract. The error appears.

We worked through all the settings and confirmed the configurations. The correlation ID is misleading. When you record the logs, the correlation ID refers to the Transaction Category not being created. This is not true as the Transaction Categories, Shared Categories and Project Categories are created and also showing in F&O.

Microsoft is now busy trying to simulate the error in their lab to see what could be the issue with the quotes.

Things to look out for.

-Make sure that the Transaction Categories are created in PO and showing in F&O.

-Make sure that the Shared and Project Categories are showing.

-Make sure that your Forecast Models and Posting Profiles are created in F&O. This is key for the tasks to sync back to the projects in F&O.

If the above is confirmed try the following:

-Create a project with no quote or contract and see if the resources can be added to tasks.

-Create a project with a contract and no quote and see if the resources can be added to tasks.

-Create a project with a contract and a quote and see if the resources can be added to tasks.

Hope this helps. Will update when we make the next progress on the issue.
jliang55 55 on at

Like (0)

Report

RE: Couldn't Assign Resources to the tasks in Project Operations

Sorry, no luck on my end.

MS Support suggested check the category, resource and posting profile from the FO side. But so far there isn't a clear answer what's happening to my particular scenario.

Spalanidurai replied to this thread that he/she resolved it by changing some dates or duration. But that didn't help in my case. See if it works for you.

Cheers,

Jimmy
jliang55 55 on at

Like (0)

Report

RE: Couldn't Assign Resources to the tasks in Project Operations

Hi Spalanidurai,

Thank you for sharing your fix. Some of my teammates with MS Project experience also suspected it's related to some dates. On the Summary tab of the Project in Dynamics, I've tried to reset the start date and due date (we've even tried to push the due date to 5 or 10 years out); but still got the same error.

MS Support suggested me check the category, resource and posting profile from the FO side. But so far there isn't a clear answer what's happening to this particular instance.

Thank you,

Jimmy