TransactionHistoryResponseModel

if the user attaches one or more binary data buffer (or file) to a transaction, then the attached binary data will be returned here

if the user attaches one or more notes (comments/text) to a transaction, then the user text/comments will be returned in this field

from dbo.location.location_code this is the original value without the calculated value of the location_prefix

example, if location_code = ''Room 101', location_prefix is 'Parent 1', then LocationFullPath would be 'Parent 1\Room 1'

example, if location_code = ''Room 101', location_prefix is 'Parent 1', then LocationFullPath would be 'Parent 1\Room 1'

example, if location_code = ''Room 101', location_prefix is 'Parent 1', then LocationFullPath would be 'Parent 1\Room 1'

Wasp-Remove-Obsolete-Field

UPDATE[WaspTrack].[dbo].[form_field_meta] SET ffm_visible_on_grid = 1 where ffm_field like '%due%date%' and form_id = 250

Lot, Date Code, Trackby Serial Number, along with possible user-defined field values help to identify the object/widget.

A reference number that the user may have entered during the capture of a transaction. Not all transactions require a reference number.

This value, along with the ItemNumber, helps to uniquely identify a container being transacted. If this field has a value, its transaction quantities are 1 and cannot exceed 1 since the TrackbyContainerId is globally unique. For example, if TrackbyContainerId-A is being created or moved into TrackbyContainerId-B, then this field will have the value of TrackbyContainerId; however, the field ParentContainerId would have value of TrackbyContainerId-B.

Wasp-Remove-Obsolete-Field