When we intentionally overbook an item, is there a way to have the conflict show up on both leads?
This is something we have considered making a additional style for. It likely won't flag the lead, but might display it in another way.
Has anything changed with this? We really need to see the conflict on both leads. We just had one where two leads had both been in the system for a while, both had the item Cornhole on them, which is no problem because we have 5. Then we increased the quantity on one lead yesterday, which put us at a total of 6. It didn't show a conflict on that lead, so everything seemed fine. Turns out, the conflict popped up on the other lead; I assume it was because the other lead was originally booked at a later date.
For many reasons, we really need the conflict to show on both leads. It's just too easy to miss otherwise.
Updating the Quantity on one lead should have caused that lead to lose it's "priority" and would have shown the conflict on that lead when it was updated or saved. I tested this in a test account and it behaved as I expected. Do you have the Lead ID's for these events? I can look into the edits that were made.
Yes, we increased the quantity on lead 3656565, but the conflict showed up on lead 3741601. I just did it again and got the same result. I left it with the conflict for now so that you can see it.
Thanks for the example. I've verified what you're doing and I think there must be a bug. Perhaps my original test was incorrect. We'll get this resolved as soon as we can.
Ok thanks. I'd still like to see the conflict on both leads if possible.
I just had a similar situation pop up. We changed the setup date on lead 3561575, which created a conflict on one item. However, that conflict only showed up on lead 3775613. This is too easy to miss if it doesn't show up on the lead we're editing.
Good point. We have a solution in mind for this, but are in the process of editing some other things in order to implement it. I'll see if we can get an alert or something put together in the meantime.
Comments have been locked on this page!