Forum Discussion
Solved
Bulk Edit Not Working
I would like to bulk edit tasks, specifically the Task Calendar. I highlight multiple rows (2 or more), select Information -> Advanced -> Calendar and then pick a calendar, but no changes are ma...
- All --
I have the same version of Microsoft Project that others are using. I just did an extensive test on the features in the Multiple Task Information dialog, and can confirm that NOTHING is working in this dialog. I tried changing the Duration for a block of tasks. No go. I tried changing the constraint type to As Soon as Possible to a block of tasks, each of which has a SNET constraint applied, and no go again. It is obvious that Microsoft has introduced a bug into Microsoft Project, and this bug NEEDS TO BE FIXED. I will report this bug to my contacts within Microsoft to see if they can get the fix moving. Thanks so much to all for reporting this.
rbuzeta,
Unfortunately the people at Microsoft support you are talking do simply do not know what they are talking about. The information you are being given is WRONG. The support people are correct on one thing, "it is not possible to make bulk changes", because it IS a bug and per Dale's response, it is being worked by Project developers.
John
Unfortunately the people at Microsoft support you are talking do simply do not know what they are talking about. The information you are being given is WRONG. The support people are correct on one thing, "it is not possible to make bulk changes", because it IS a bug and per Dale's response, it is being worked by Project developers.
John
Hi John-project
It's a BUG, for me there is no doubt about that. Apparently the support people who wrote in response to my report don't seem to know what they're talking about, I agree with that too. It has not been my intention to contradict, in any way, the expressions that say that it is a bug, since it is obvious that it is. I only thought it was important that the community know that, more than a month after this bug was detected, a solution has not yet been deployed and, on the other hand, there is a person who signs as Microsoft Support who affirms that this is not a bug (sadly). However, despite the written communications to my email, I appreciate your clarifications, I prefer to think that this forum has better information than the Support people, I choose to believe that the people at Microsoft are already working on it and I will wait for the deployment of the solution. Thx again.
It's a BUG, for me there is no doubt about that. Apparently the support people who wrote in response to my report don't seem to know what they're talking about, I agree with that too. It has not been my intention to contradict, in any way, the expressions that say that it is a bug, since it is obvious that it is. I only thought it was important that the community know that, more than a month after this bug was detected, a solution has not yet been deployed and, on the other hand, there is a person who signs as Microsoft Support who affirms that this is not a bug (sadly). However, despite the written communications to my email, I appreciate your clarifications, I prefer to think that this forum has better information than the Support people, I choose to believe that the people at Microsoft are already working on it and I will wait for the deployment of the solution. Thx again.