Bug 7 - System throws raw technical error instead of proper validation message on Purchase Request creation
Summary: System throws raw technical error instead of proper validation message on Pur...
Status: OPEN
Alias: None
Product: Smartwas
Classification: Unclassified
Component: Sales (show other bugs)
Version: unspecified
Hardware: PC Windows
: Normal Medium
Assignee: Hemanth (Hemanth)
URL:
: 11 13 15 19 23 32 (view as bug list)
Depends on:
Blocks:
 
Reported: 2026-05-27 09:54 UTC by Karunakaran (Karunakaran)
Modified: 2026-07-03 06:53 UTC (History)
1 user (show)

See Also:
Associated Test Case ID:
Triaged By: ---
Root Cause Analysis (RCA):
Resolution Summary / Fix Details:
Impact Area:

Attachments
image (228.20 KB, image/png)
2026-05-27 10:39 UTC, Karunakaran (Karunakaran) 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Karunakaran (Karunakaran) 2026-05-27 09:54:24 UTC 
Location: Sales→Internal Sales→Edit Internal Sales Order→Delivery Notes→Create Delivery Notes→Purchase Request

When the user clicks on Create Purchase Request, the system shows an error message “Invalid argument: one of the given objects, null” instead of a proper validation message.
Comment 1 Karunakaran (Karunakaran) 2026-05-27 10:39:24 UTC 
Created attachment 3 [details]
image

image
Comment 2 Karunakaran (Karunakaran) 2026-06-05 06:10:56 UTC 
*** Bug 11 has been marked as a duplicate of this bug. ***
Comment 3 Karunakaran (Karunakaran) 2026-06-05 06:11:17 UTC 
*** Bug 15 has been marked as a duplicate of this bug. ***
Comment 4 Karunakaran (Karunakaran) 2026-06-05 06:11:45 UTC 
*** Bug 19 has been marked as a duplicate of this bug. ***
Comment 5 Karunakaran (Karunakaran) 2026-06-05 06:12:07 UTC 
*** Bug 23 has been marked as a duplicate of this bug. ***
Comment 6 Karunakaran (Karunakaran) 2026-06-05 06:12:27 UTC 
*** Bug 32 has been marked as a duplicate of this bug. ***
Comment 7 Karunakaran (Karunakaran) 2026-06-05 06:22:32 UTC 
*** Bug 13 has been marked as a duplicate of this bug. ***