I understand where you're coming from - I wouldn't expect this to take priority. I do however continue to think that having a delete feature / account closure feature is fundamental to any SaaS application today - especially one aimed towards businesses.
What continues to frustrate me is being told that you as Yammer are unable to actually carry out this process yourself. That doesn't make any sense to me - you have access to your servers don't you?
I think there's a gap in what Support is saying and what any slightly technical user knows is possible - even if the "feature" isn't available on the front end.
I'm sorry for the lengthy delay before the response. Hopefully we'll get better at this in the future.
I agree - this functionality is justifiable. However, we have many things we'd like to implement, and this one wasn't prioritized for the reasons I mentioned.
I'm sorry we told you this couldn't be done. In actuality, this reached the attention of our engineers quite late. As I understand, you first spoke with our support staff, and then with our community manager, after this thread. You're right about the gap - this is theoretically possible, but it just hasn't been implemented. At all.
It's also not exactly simple: we denormalize data in lots of places, there are plenty of nasty side cases relating to inter-related networks, the data lives in many separate systems, and of course everything is backed up. Getting rid of a single network is more than just a DELETE query. This is lots of code to write and test.
Comments
Thanks for being upfront about it - finally!
I understand where you're coming from - I wouldn't expect this to take priority. I do however continue to think that having a delete feature / account closure feature is fundamental to any SaaS application today - especially one aimed towards businesses.
What continues to frustrate me is being told that you as Yammer are unable to actually carry out this process yourself. That doesn't make any sense to me - you have access to your servers don't you?
I think there's a gap in what Support is saying and what any slightly technical user knows is possible - even if the "feature" isn't available on the front end.
I'm sorry for the lengthy delay before the response. Hopefully we'll get better at this in the future.
I agree - this functionality is justifiable. However, we have many things we'd like to implement, and this one wasn't prioritized for the reasons I mentioned.
I'm sorry we told you this couldn't be done. In actuality, this reached the attention of our engineers quite late. As I understand, you first spoke with our support staff, and then with our community manager, after this thread. You're right about the gap - this is theoretically possible, but it just hasn't been implemented. At all.
It's also not exactly simple: we denormalize data in lots of places, there are plenty of nasty side cases relating to inter-related networks, the data lives in many separate systems, and of course everything is backed up. Getting rid of a single network is more than just a DELETE query. This is lots of code to write and test.
I hope that helps explain our response.