Changing a TransactionEntry Qty using QSRules

You're going to have to check the for the existence of tag-along items and update their quantity in your code. No additional logic is called when you modify the transaction through QSRules.

Well, maybe I'm wrong... I thought that ..TranactionEntries.Add(...) just inserted the item without looking for any special properties - Tag Along, Parent Child, discounts, sales, customer prices, etc... Maybe it's smarter than I thought...

I know that Tag-Along's do work. Customer Price Level's will work only if you have the UseComponentPrice argument set to False. This probably also applies to Sale Prices, but I haven't tested it. I do not believe that discount schemes are applied - again, I haven't tested that either.

Okay, I've now identified the problem. Not sure if it's a bug in RMS or a "design feature". Try this in the standard transaction window:

1. Switch to Work Order mode (CTRL F2)
2. Add an item to the transaction that has a tag along item. (F2)
3. Tender the transaction (F12)
4. Recall the work order that you just created (F11)
5. Change quantity of the item you added in step 2.
6. Tag along item quantity does not change.

Could somebody tell me if this is a bug or a feature?

"Sim> Discount schemes are definitely applied and work fine. The only thing I have

The UI is handling the update of the quantity for tag-along. With POS, when you add an item to a transaction it somehow remembers that the tag-alongs are linked to the first item. So when you change the qty of the first item, the UI goes and changes the qty for the rest of them. When you recall a transaction, the UI does not check for this link, and so each individual transaction entry is treated as a stand-alone item. I guess you could consider it a bug. You could open a support incident about it, so that they can fix it.

As for how this affects your add-in, it just means you need to check for tag-alongs in your code. I'm sure they left it up to the UI on purpose, rather than letting QSRules handle this.