How did you verify that the event handler is not invoked?
I created and deployed a simple beforeRemove event handler in codeless (which results in a JS handler from the implementation perspective). Here’s what it looks like:
Here’s the log from the execution of the event handler:
21:01:52 | SERVER_CODE | INFO | [5299] Building ServerCode Model for path (/opt/backendless/repo/840386aa-ff5c-8c9f-ff46-943134b88e00/files/servercode/CODELESS/default/PRODUCTION)
21:01:52 | SERVER_CODE | INFO | [5299] ServerCode Model built in 7ms
21:01:52 | SERVER_CODE | INFO | [5299] [14f3f6c6-8525-4518-8e85-68a8a9cd4662] [INVOKE HANDLER] user.beforeRemove
21:01:52 | SERVER_CODE | INFO | [5299] in before remove
21:01:52 | SERVER_CODE | INFO | [5299] 3AA880DE-BE6C-49EA-B9B5-B1D0082CCF40
21:01:52 | SERVER_CODE | INFO | [5299] Processing finished in 34.912ms
Hi @mark-piller, did you have a chance to see my response. I would like to add server side logic that rely on the handlers before delete update create and bulk (as I implement multi-tenant service that should either add the organization value using handlers or verify user can delete / update / bulk action them.
I feel like I’m missing something and not necessarily found a bug.
Please assist.
Question, I saw that there are limitation on the number of handlers/services, maybe it applies also during deployment and you just ignore my handlers that are connected from the IDE?
In Console, you retrieve a table with params that you choose, it’s triggered ‘find’ handler. But if want to trigger ‘loadRelations’ you must use the method from SDK - loadRelations, its external API.
Example here - Relation Paging - Backendless SDK for JavaScript API Documentation