TNew auto populating order notes

This changed with one of the minor (unannounced) software updates to TNEW that happened a few weeks ago. Not sure if it's expected behavior or a regression/bug, but it would require a change in the TNEW application code to stop the behavior you observed.

If they really bug you, you could probably write a SQL server scheduled job that clears these out when there's no data, but since the TNEW team doesn't tell us when they make minor updates like this, your job would be liable to break without warning.

<soapbox>

I strongly believe that the TNEW team should be notifying us prior to minor updates, either through a forum post or email list message. These update changes are currently only posted in the documentation after the fact, meaning delicate customizations can break without warning, and forcing us admins to be reactive instead of proactive. :-(

</soapbox>

Thanks for your quick reply Nick.

I'm glad to know why it's happening at least, but completely agree that a heads up would have been useful!

We've experienced this here, too. A known bug. Please report it via a support ticket, as I believe they can fix it now, or at least they could on 3/25.

(Interesting: could this be something that must be fixed site-by-site?)

Not fixed. I see these are appearing in our orders again, too. I'll be resubmitting our support ticket shortly...

On 3/25 I reported in a "pending - dev review" support ticket that they had stopped appearing in our orders. I now see that sometime in the last week or so they've started appearing again, which I've also reported.

Thanks everyone! In our ongoing efforts to address issues reported by our users, a minor change was made that inadvertently affected the way that order notes are handled on TNEW behind the scenes. Regardless of the customer entering anything in, TNEW is saving a blank note of "CustomerNotes:" to the order notes field. This issue was introduced with our last patch, when v5.5.18.49 was pushed out to all v5.5 TNEW sites.

We have a fix in place in our internal QA environment, and will be pushing fixes out to all QA TNEW sites early next week. If you are experiencing this additional order note on your site and would like to help test the changes, please submit a TASK ticket and we will let you know as soon as the patch is ready for testing on your QA site.

We update the Release Notes section of the TN Express Web User guide as soon as a known defect has been resolved. So as soon as this fix is available, you will see it posted there.

Best,
Karyn

Thanks so much!! 

Carol

Hi

We are also experiencing this automatic message that populate in our customer's order (customer's notes: ;) and for some instance it shows up twice in 2 lines. Aside from this issue our patrons are receiving an sql error in their confirmation email as it shows below.

Exception: System.Data.SqlClient.SqlException (0x80131904): Invalid Procedure Index at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior) at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) at Tessitura.WebAPI.ExecuteLocalProcedureCommand.Execute() at Tessitura.WebAPI.Tessitura.ExecuteLocalProcedure(String SessionKey, Int32 LocalProcedureId, String LocalProcedureValues) at TNEW.Objects.CartEmailData.LoadData()

Is there anyone also experiencing this problem?

Thanks

Eric Lazaro

RWB - Database Administrator

Hi Eric,

The issue with your order confirmation email sounds like you may not have the current version of the TNEW Email templates. I've gone ahead and opened a TASK Support ticket on your behalf and you will receive a copy via email. Someone from our support team will be in touch to assist you shortly.

Best,
Karyn 

P.S. We are still reviewing the fix for the CustomerNotes: ; issue and hope to have an update for everyone later this week.

Hi Karyn

Thank you very much! :)

Hello everyone,

Just a quick update regarding customer notes being recorded on all web orders. A fix has been placed on all v5 & v5.5 QA sites to resolve this issue and will be deployed to all live sites tomorrow, May 5. 

Please feel free to submit a TASK ticket in the Web Products Workspace if you have any other questions.

Thank you,

Melissa Champ 

Thank you so much for the heads up!!