Process returns for serialized items in POS
On the Inventory tab, on the Store inventory operations FastTab, set the Enable validation of serial numbers on POS returns option to Yes.
To configure serial number validation for an organization after the Unified return processing experience in POS feature is turned on, go to Retail and Commerce > Headquarters setup > Parameters > Commerce parameters in Commerce headquarters. Users can continue to process a return against a serial number that differs from the serial number that was originally sold. In the Commerce version 10.0.20 release and later, the message that users receive is only a warning message. This capability can warn users if the serial number that is being returned differs from the original serial number that was sold. When the Unified return processing experience in POS feature is turned on, organizations can perform a validation on returns of serial number–controlled items through POS. Options for validating serialized returns For information about others capabilities that this feature provides when it's turned on, see Create returns in POS).Īfter the feature is turned on, it can't be turned off. To use serial number validation during return order processing in POS, you must turn on this feature. I just don’t see how else I would have figure this thing out.In the Commerce version 10.0.20 release and later, a new feature that is named Unified return processing experience in POS is available. I hope I don’t get in trouble of advising people to use. 2 steps rather than trying to it all in one process. Then after that process is finished, I can then override the price.
In other words, I needed to create the cart line and save it to commit it to the salesTransaction first. Causing a cryptic error about unit of measure/quantity.
What I found was that it code used the salesTransaction object rather than the cartLine to get the unit of measure. I put a breakpoint and run through the process. Then right click, Go to Decompiled Definitionĥ. Navigate to the method that caused the error. Select the dll that is referenced and click on Enable Debugging. NET Reflector > Generate PDBs (this will pop up a dialog to select the assembly)Īlternatively, from your solution explorer. There are a couple of ways you can do that.
When you install – I would recommend both the desktop and the visual studio extensionģ. You can use the trial for 14 days or just active it with your serial number Using this tool, I was able to make sense of the problem.īelow are the steps to use. NET reflector (this is where you need an experienced retail developer). Source=.WorkflowĪt .(RequestContext context, Cart newCart, SalesTransaction salesTransaction, Dictionary`2 salesLineByLineId, CartLineValidationResults cartLineValidationResults)Īt .(RequestContext context, SalesTransaction salesTransaction, SalesTransaction returnedSalesTransaction, Cart newCart, Boolean isGiftCardOperation, IDictionary`2 productByRecordId)Īt .(SaveCartRequest request)Īt .SingleRequestHandler`2.Execute(Request request)Īt .CommerceRuntime.Execute(Request request, RequestContext context, IRequestHandler handler, Boolean skipRequestTriggers)Īt .(SaveCartRequest request)Īfter many hours over the course a few days we struggled. Message=Object reference not set to an instance of an object.
System.NullReferenceException was unhandled by user code The modification was overriding the price. Unit of measure and quantity fields were populated correctly. I was sure the object was not null and I had passed the right thing to it. The error we got was complaining about the a method to validate the Unit of measure and Quantity. We were working on a development project and we struggled to make sense out of the error. This is an example of something I would have not figured out without my colleagues. It really requires some dedication and focus to be a POS developer.