At some point recently, transferinventoryitems cross-collection stopped respecting the 'NewStackValues' property.
For months this has been working, but all of a sudden it does not seem to be. The request passes, but the item does not receive the new stack values.
Ok, this is sort of a breaking change, is there any info about it?
Thanks for reporting this issue. We'll take a look to see if we can reproduce it.
We spent some time looking into this. There is definitely an inconsistency between single-collection transfer and cross-collection transfer when it comes to NewStackValues. We don't think the behavior has changed recently, though (it seems to have always been this way).
What I can say is that, yes, it appears like we aren't respecting NewStackValues in the cross-collection scenario. We'll look into correctly adding support for that.
I know for sure that this was working at one point. I wrote the code that relied on it months ago. This was a core test case.
The fix for this should be deployed now. All versions of transfer should work as follows:
if (the stack exists) do not update the display properties.
else if (new stack values include properties) set the properties for the new stack.
else copy source stack properties to target stack properties.
36 People are following this question.
