Well, I have changed the 15,000 records manually - still no word from Bloomerang and I see this is still not a priority. What users are they actually listening to?
Currently MANUALLY updating one custom field on 15,000 transactions in an effort to clean up an "inherited" data base. This feature would save me weeks of time. Over 67 weeks ago I submitted a request for a quote to have Bloomerang do this for me; have hear nothing from them. I'll get a clean database without their help I guess.
Please consider prioritizing this functionality. A keying error was made to approximately 45 transactions (the incorrect sub-appeal was used) and without the ability to do a mass update on a custom transaction field, each transaction will need to be manually changed, clearly not the best use of time.
Bloomerang provides the ability to add custom fields yet restricts the ability to update the fields. via a batch import. What is the point of having this functionality if updates to a transaction can only by done manually after a transaction has been added?
Not being able to do this is mind-boggling. To be honest, I want to be able to bulk update anything I want to on any view/report. To have to ask Support to do this in the db itself is inefficient. I waited months the last time I asked for help adding a custom field to existing files. Now, every transaction that has been entered since is missing the field. :(
Well, I have changed the 15,000 records manually - still no word from Bloomerang and I see this is still not a priority. What users are they actually listening to?
Currently MANUALLY updating one custom field on 15,000 transactions in an effort to clean up an "inherited" data base. This feature would save me weeks of time. Over 67 weeks ago I submitted a request for a quote to have Bloomerang do this for me; have hear nothing from them. I'll get a clean database without their help I guess.
Please consider prioritizing this functionality. A keying error was made to approximately 45 transactions (the incorrect sub-appeal was used) and without the ability to do a mass update on a custom transaction field, each transaction will need to be manually changed, clearly not the best use of time.
Bloomerang provides the ability to add custom fields yet restricts the ability to update the fields. via a batch import. What is the point of having this functionality if updates to a transaction can only by done manually after a transaction has been added?
Not being able to do this is mind-boggling. To be honest, I want to be able to bulk update anything I want to on any view/report. To have to ask Support to do this in the db itself is inefficient. I waited months the last time I asked for help adding a custom field to existing files. Now, every transaction that has been entered since is missing the field. :(
Mass update acknowledgement status