Hello Katherine,

It is now, May 26, 2021 and this issue has not been addressed.  My question is why?  What is the difficulty with bringing QB up to a basic standard on a very critical, procurement document.  It is obvious that there was work performed to allow the SKU field to be turned on in the template settings. So why is it not working, as intended? Is there any layer of transparency that you can offer, other than a politically correct response to side-step the issue?  Is there no hope that this has been pre-planned on a future release with an updated version number to look forward to?  I think this is the most frustrating part of reading these customer threads is that there literally is no response from QB on this critical issue.  Can you provide an explanation of the complexity of the work needed to correct the issue, because I am missing something.  I would appreciate your guidance to help me understand this situation.

regards,

Bob