You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Mridul Pathak (Jira)" <ji...@apache.org> on 2026/09/16 12:03:00 UTC

[jira] [Closed] (OFBIZ-13594) updatePartyInvitation silently no-ops on a nonexistent record

     [ https://issues.apache.org/jira/browse/OFBIZ-13594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mridul Pathak closed OFBIZ-13594.
---------------------------------
    Fix Version/s: Upcoming Branch
                   24.09.08
       Resolution: Fixed

> updatePartyInvitation silently no-ops on a nonexistent record
> -------------------------------------------------------------
>
>                 Key: OFBIZ-13594
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-13594
>             Project: OFBiz
>          Issue Type: Bug
>          Components: party
>    Affects Versions: Upcoming Branch, 24.09.07
>            Reporter: Mridul Pathak
>            Assignee: Mridul Pathak
>            Priority: Minor
>             Fix For: Upcoming Branch, 24.09.08
>
>
> {{updatePartyInvitation}} builds its value via {{makeValue('PartyInvitation', parameters)}} rather than fetching the existing row first. The original minilang did an {{<entity-one>}} lookup that would fail if the target {{partyInvitationId}} didn't exist. As converted, updating a nonexistent invitation matches zero rows on the underlying UPDATE and returns success anyway. Reachable via the Party Manager "Edit Party Invitation" UI for a stale/deleted invitation id.
> Needs fixing: fetch the existing {{PartyInvitation}} first and return an error if not found, before applying the update.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)