I got a couple of actions in Breww that can’t be uploaded to my accountancy program (VIsma) - (credit note payments/ bank payments). I work around this, but they throw a sync message that I can ignore, but I can’t bulk stop attempting the upload and not really keen to manually stop about 50 messages.
Result is that I miss important/relevant messages about sync errors.
Is it possible to add a bulk stop attempting feature? Or allow certain specific actions to not be uploaded?
As you say, it’s important to keep the sync error list clear so that important messages don’t get missed.
We have a very busy schedule, so while I appreciate it’s a bit of a tedious task to have to update these manually, I don’t think it likely that we’ll get to this request in the short term, I’m sorry (it’s also not got any votes yet).
In the short-term, given the importance of not missing important messages, it’s probably worth doing them one-by-one, I’m sorry!
We’ll keep this request open to hopefully be implemented in the future, but I wanted to be transparent that it’s unlikely to happen soon.
I know it is minor in the scheme of things, but his is still an issue for me. As I have a big amount of irrelevant sync errors coming in every week (currently I have 184 irrelevant ones and 1 important one) - I do not check them and miss the occassional important one.
It would be great if I would be able to bulk discard them and/or toggle some actions on off (in my case cash/bank payments from breww→visma, credit note allocations brew–>Visma)
The problem with a button to bulk stop attempting upload is that it feels like a misfeature. Clearing the messages doesn’t resolve the cause of the problem, and you’ll continue to get more and more over time.
Are you unable to resolve the root cause of the messages? (Usually, they come from some configuration that the accounting platform is rejecting, and can be resolved by correcting the configuration.)
The root cause is that the Visma platform cannot accept the requests breww sends them as Visma does not allow payments/allocations from breww to visma in the case of creditnotes.
We checked this at the beginning and Max checked it again a while back, to no avail.
Ah ok. Can you open a quick support ticket with a link to this thread in it, and grant us account access, and we’ll look into this further for you. If this is a limitation in Visma, we should be able to handle it without ever raising a sync message in the first place (which sounds like the best overal solution to me).
This is a configuration issue rather than a problem in itself. When the configuration issue is fixed, there won’t be a need to bulk stop uploading, so I’ll close this FR as not required.