Crash when selecting Purchase Orders tab

When clicking on the Purchase Orders tab in version 18.1.4, the following error notice appears:

Internal Error
18.1.4 (Desktop)
/purchase-orders?FileID=58d398ba-08f3-477e-9034-0e3a3bb609be
System.NullReferenceException: Object reference not set to an instance of an object
  at ManagerServer.HttpHandlers.Businesses.Business.Table.GetCellsFromCustomFields (Manager.Model.CustomField[] customFields, System.Collections.Generic.Dictionary`2[TKey,TValue] values) [0x0004d] in :0 
  at ManagerServer.HttpHandlers.Businesses.Business.PurchaseOrders.PurchaseOrders.GetRows () [0x00252] in :0 
  at ManagerServer.HttpHandlers.Businesses.Business.Table.Get () [0x00041] in :0 
  at HttpFramework.HttpApplication.ProcessRequest (HttpFramework.HttpRequest request, HttpFramework.HttpResponse response) [0x0040d] in :0 
  at ManagerServer.HttpApplication.ProcessRequest (HttpFramework.HttpRequest request, HttpFramework.HttpResponse response) [0x00566] in :0 

This does not occur for any other tab.

I’m not able to reproduce this issue but it must be something to do with custom fields on purchase orders.

Try the latest version (18.1.5). I tried to fix the issue based on the posted error.

Yes. I have a date-type custom field defined for purchase orders. When set to show as a column, the tab crashes the program when selected, regardless of whether any purchase orders have content in that custom field. When not set to show as a column, and whenever set to show on printed documents, it does not crash, whether the field has content or not. In other words, the presence of a custom field set to show as a column causes the crash.

But this only happens for Purchase Orders. I have other date-type custom fields for Fixed Assets. They cause no problem when set to show as columns.

All this testing has been in the Northwinds test business. I also defined date-type custom fields in other test businesses with no problems, including in Purchase Orders.

I will update to 18.1.5 and let you know the results.

Totally fixed in 18.1.5. I tried all combinations of showing as column, on printed documents, with different date formats, and both with and without content in the custom field.