so I guess this "resource duration" shouldnt be used when the resource itslef isnt marked as "driving" (this is why it didnt work, because when I marked "driving", the task immediately completed itself).
thanks !
Member for
22 years 9 months
Member for22 years9 months
Submitted by Alexandre Faul… on Wed, 2009-10-28 18:20
when a resource is "driving", you can enter a resource duration value to indicate how long the resource will work on that particular task (say: 4 days on a 5 days task), and a lag to say that the resource will start working on day 2 of the task duration
a "driving" resources workload will let P3 to calculate the task duration by dividing Budgeted Qty by Units per day; when the resource is not "driving", P3 multiplies the task duration by Unite per day to calculate Budgeted Quantity
thanks, but I forgot to mention that I already scheduled everytime I changed something (even if putting 0 in res duration doesnt need it to see the changes)
it seems that the multi-resource is not causing this, since others multi-resource tasks have been correctly completed.
but in the resource floating window, I have a res lag/duration with something in it. when I put 0 in res lag it does nothing, but when I put 0 in res duration, it now works and the task completes normally with no quantity to complete.
Member for
22 years 9 monthsRE: Quantity to complete question !
Johnny,
you just cannot use this field when the resource is not driving this particular assignment
Alexandre
Member for
20 years 1 monthRE: Quantity to complete question !
oh okay.
so I guess this "resource duration" shouldnt be used when the resource itslef isnt marked as "driving" (this is why it didnt work, because when I marked "driving", the task immediately completed itself).
thanks !
Member for
22 years 9 monthsRE: Quantity to complete question !
Johnny,
when a resource is "driving", you can enter a resource duration value to indicate how long the resource will work on that particular task (say: 4 days on a 5 days task), and a lag to say that the resource will start working on day 2 of the task duration
a "driving" resources workload will let P3 to calculate the task duration by dividing Budgeted Qty by Units per day; when the resource is not "driving", P3 multiplies the task duration by Unite per day to calculate Budgeted Quantity
Alexandre
Member for
20 years 1 monthRE: Quantity to complete question !
thanks, but I forgot to mention that I already scheduled everytime I changed something (even if putting 0 in res duration doesnt need it to see the changes)
Member for
16 years 11 monthsRE: Quantity to complete question !
Hi
schedule it once again
Member for
20 years 1 monthRE: Quantity to complete question !
hi again
it seems that the multi-resource is not causing this, since others multi-resource tasks have been correctly completed.
but in the resource floating window, I have a res lag/duration with something in it. when I put 0 in res lag it does nothing, but when I put 0 in res duration, it now works and the task completes normally with no quantity to complete.
whats this res duration exactly ?