RELATED IDEAS
Improve custom services or AT LEAST add a warning about data loss
We recently tried to update the name of one of our custom services, not realising that due to the way custom services are added, changing the name of the service would completely delete the original service and all of its data and create a new one with no data in the new name.
Please can you either:
1) Ideally, update the way we are able to add in custom services, whereby each custom service can be individually added, saved and edited (rather than the large text box with commas separating each service that you have now)
or 2) at a minimum, add a warning box to the custom service section explaining that custom services cannot be renamed without losing data, so no other poor companies make the same mistake as we did and lose their data.
Hi All,
You will be pleased to hear that we have released the ability to customise custom services in our recent release. This will update the name of the service and the corresponding tasks without losing any progress on the tasks.
Thanks for your feedback.
James
Hi Marjorie,
I agree. I did the same mistake once. One of the great advantages of BM is that one can add and adapt services to their practice. There is no sufficient warning as to what happens when you modify these. Also, and I believe that it has already been mentioned elsewhere, you only have a limited number of task statuses available for custom services. I think there is a broader conversation to have on the implications of changing this and how it could affect other parts of the program. So for the moment, I accept that adding custom services is workable. One just has to understand the limitations of using them.