Batch Split error AttributeError: 'StockEntry' object has no attribute 'shift'

[andrewhartono]

Information about bug

Error when creating split batch

AttributeError: 'StockEntry' object has no attribute 'shift'

Module

accounts, stock, buying

Version

ERPNext: v13.19.0 (HEAD)

ERPNext Support: v0.2.1 (master)

Installation method

FrappeCloud

Relevant log output / Stack trace / Full Error Message.

No response

[stale[bot]]

This issue has been automatically marked as inactive because it has not had recent activity and it wasn't validated by maintainer team. It will be closed within a week if no further activity occurs.

[ankush]

shift doesn't exist anywhere in batch / stock entry code.

When this happens click on "copy error to clipboard" / report and share content here.

[andrewhartono]

### Request Data

{ "type": "POST", "args": { "item_code": "ajoss1", "batch_no": "B840C3D", "qty": 2, "warehouse": "Warehouse1 - ACH" }, "headers": {}, "error_handlers": {}, "url": "/api/method/erpnext.stock.doctype.batch.batch.split_batch" }

### Response Data

{ "exception": "AttributeError: 'StockEntry' object has no attribute 'shift'" }

[andrewhartono]

@ankush since the issue is closed, should i open new issue or continue with this threat? can it be opened again?

[ankush]

@andrewhartono share the full traceback, please. The message you shared doesn't contain the traceback.

Is it possible that this is error from your customization? (like servicer script maybe?)

[andrewhartono]

@ankush i use frappecloud so there is no customization Frappe Framework: v13.23.0 (HEAD) ERPNext: v13.23.3 (HEAD) how to get the full traceback? there is no error log on this error

[stale[bot]]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[deepeshgarg007]

@andrewhartono Just checked this and it worked fine for me, please add more info to replicate and reopen if the issue still persists