Bug 35244 - AcqItemSetSubfieldsWhenReceived not working after upgrade
Summary: AcqItemSetSubfieldsWhenReceived not working after upgrade
Status: RESOLVED DUPLICATE of bug 35273
Alias: None
Product: Koha
Classification: Unclassified
Component: Acquisitions (show other bugs)
Version: 23.05
Hardware: All All
: P5 - low major (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-03 08:02 UTC by Klas Blomberg
Modified: 2023-11-16 08:39 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Klas Blomberg 2023-11-03 08:02:20 UTC
AcqItemSetSubfieldsWhenReceived not working after upgrade to 23.05

Item fields are not updated when receiving items in acquisition
Comment 1 Katrin Fischer 2023-11-06 22:17:09 UTC
I could not test in 23.05 yet, but on the current development version this appears to work ok:

*  AcqItemSetSubfieldsWhenReceiptIsCancelled: 7=-1
*  AcqItemSetSubfieldsWhenReceived: 7=1

When received NFL switched to 1 = Not for loan.
When receive was undone, NFL switched to -1 = 0n Order.

So this appeared to work right.

Can you share your mappings maybe? A step by step?
Comment 2 Klas Blomberg 2023-11-10 10:23:06 UTC
Our settings are:

AcqItemSetSubfieldsWhenReceiptIsCancelled 7=-4
AcqItemSetSubfieldsWhenReceived 7=-3

Vaggeryd library have also found this bug on 23.05, their settings are
AcqItemSetSubfieldsWhenReceived 7=0
Comment 3 Katrin Fischer 2023-11-10 10:31:07 UTC
Hi Klas, let's try to find the difference in our testing. Could you provide a step by step what you do that helps make the bug visible?
Comment 4 Katrin Fischer 2023-11-10 10:31:36 UTC
Ah and also: which is your exact version of 23.05 - the third digit?
Comment 5 Katrin Fischer 2023-11-13 08:50:48 UTC
It would be really good to have more information here in order to be able to get closer to the problem.
Comment 6 Klas Blomberg 2023-11-15 14:21:15 UTC
This seems to be the same problem as bug 35273

*** This bug has been marked as a duplicate of bug 35273 ***
Comment 7 Katrin Fischer 2023-11-16 08:39:29 UTC
(In reply to Klas Blomberg from comment #6)
> This seems to be the same problem as bug 35273
> 
> *** This bug has been marked as a duplicate of bug 35273 ***

Hi Klas, that explains why I wasn't able to break things, thanks for resolving. That's why I was asking about your exact version. I would have then repeated my tests with that version to narrow it down.