Forum Discussion
Problema asignacion de recursos
Sorry but I don't know what Project Professional 2311 is. Are you referring to the build version? If so, the latest version for Project Pro 2019 is, version 2310 (build 16924.20150 CTR) released Nov 14. Using that version this is what I get (Standard calendar):
First resource assigned -
Second resource assigned -
Third resource assigned -
So, I'm not sure exactly what you are looking for but my results differ from yours.
John
Hello Jhon. John-project
Thank you, as always, for your valuable collaboration.
The version that I am using of Project Professional is the one shown in the following image, and that I update in File > Account > Update Options > Update Now
...and the results that Project currently shows me when consecutively assigning resources R1, R2 and R3, to a Work Type task of 1 day Duration, are those shown below, which seems incorrect to me (?)
I tried with previous versions and I get the desirable result that you included in your previous answer.
Ignacio M.
- John-projectNov 24, 2023Silver Contributor
Yup, that's wrong. I finally found what update channel I think you are on (Microsoft Insider program, release notes current channel preview). There is a newer update dated November 20, version 2311 (build 17029.20038). Maybe that fixed something.
https://learn.microsoft.com/en-us/officeupdates/current-channel-preview
You might try checking that out.
John
- Ignacio_MartinNov 24, 2023Iron Contributor
Thanks John for your suggestion, although it was already updated to the latest version.
This compilation must refer to aspects of other Office applications, which do not affect Ms Project.
Thus, I must assume that there is an error in the results that the software gives and that it should be corrected as soon as possible, since it affects programming situations that may be important for users, as is probably the case that was raised in this same thread of discussion @EduRuizAcciona, and which has been the clue that led to identifying the error.
I will communicate this more than likely error to Microsoft through the ordinary channel, although I think there may be a member of this blog (Mr. Dale for example), who is seeing it, and has a greater influence than me to report more quickly, and to whom I will be very grateful.
Ignacio M.
- John-projectNov 24, 2023Silver Contributor