Capture relate action API Before Save Script

[Maarten]

I want to capture in the API Before Save Script if a user is being related to a specific Team. If so, I want to throw a recordService\throwForbidden error.

When I relate a User to a Team, then this API call is created:

api/v1/Team/65aec3d57181bc2f7/users

The body of the call is:

{
"ids": [
"6050a05e919a9f3de"
]
}


However, when I create an API before save script on the Entity Team, that checks if the id of the team is a specific ID, then it's not being triggered.
If I update for instance the description field of the Team, then it's triggered.

Is the relate action not caught by the Team entity API before save script?
I thought about using the API before save script of the Entity User, but then I don't know what Team the user being attempted to be added to. I can only retrieve all teamIds. That's not sufficient.

Is there another way to catch this event and throw an error?

[yuri]

API Before Save won't work when you relate records via a relationship panel (dropdown > Select). You can disable this functionality to leave the User edit as the only way to add/remove teams.

In the API-Before-Save script you can compare the previous teamsIds and new teamsIds. You can check whether a specific ID was set before, whether a specific ID is set now.

[rabii]

Hi,

The reason why it won't work is first, team and user are linked in a middle table (TeamUser) so you don't have access to the field users on the team to check if there is any change. In your situation i would reach out to save error handlers, they are very useful https://docs.espocrm.com/development...error-handlers

Check out a tutorial i have written on how to use them below

https://forum.espocrm.com/forum/developer-help/developer-tutorials/92483-save-error-handlers-throw-backend-exception-handle-in-frontend-when-saving-a-record

[Maarten]

Great, I'll give this a go!