Custom Request fails with "uid undefined" after upgrading from 2.0.17 to 2.0.22

Hi everyone,

I recently upgraded NocoBase from version 2.0.17 to 2.0.22 and ran into an issue related to a Custom Request.

In my setup, I have a button that triggers a Custom Request. After upgrading, whenever I click this button, the request fails with the following error:

WHERE parameter "uid" has invalid "undefined" value

  • This setup was working perfectly in 2.0.17
  • I didn’t change any logic or configuration
  • After rolling back to 2.0.17, the issue disappears completely

So it seems like something has changed between these versions regarding how uid is handled in Custom Requests or query building.

Has anyone experienced a similar issue after upgrading? Any guidance or pointers would be greatly appreciated. Thanks!

Thank you for reporting the issue. Please wait while we fix it.

1 Like