Workspace related list inline edit bypasses server-side validation entirely

[MelchiorNow]

---

Title: Workspace related list inline edit bypasses server-side validation entirely

Description:

In a Zurich workspace, inline editing a field in a related list completely ignores server-side validation. Any value can be saved without restriction or error feedback, regardless of the validation logic in place.

Observed behavior:

We have validation logic on a custom table. When editing from the classic backend form, everything works as expected — invalid values are blocked and error messages are displayed. When editing the same field via inline edit in a workspace related list, the save always goes through with no error shown.

What we've tried:

• Before Business Rule with setAbortAction(true) + gs.addErrorMessage → value is saved anyway, no error displayed
• onCellEdit client script with callback(false) → save is blocked but no error message is shown to the user
• onCellEdit with g_form.showFieldMsg / g_form.addErrorMessage → g_form not available in workspace context

Question: What is the supported mechanism to enforce server-side validation AND display a meaningful error message to the user during workspace related list inline edit in Zurich?

Release: Zurich

---

[Ankur Bawiskar · Accepted solution]

@MelchiorNow 

onCell edit doesn't work in workspace

Before update business rule should work fine

Is the BR and the table in same scope?

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Ankur Bawiskar · Accepted solution]

@MelchiorNow 

onCell edit doesn't work in workspace

Before update business rule should work fine

Is the BR and the table in same scope?

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Ankur Bawiskar · Accepted solution]

@MelchiorNow 

it worked fine for me

I was able to stop the update in related list in SOW

See below

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[MelchiorNow]

Thank you! That's exactly the issue