Reply to message

And what is the status of this as this is beyond frustrating. We just updated to QB2022 and the issue is still present. How does it take all of these engineers this long to fix it? Its a complete joke!