524
Hi,
I am writing a plugin for creating an account and check whether the account name already exists or not. if already exists, then we should not allow to create the account. My question is in plugin registration, which event pipeline we have to chose, prevalidation or preoperation ?
*This post is locked for comments
I'm not really convinced by the answers. Andrew has a good point.
What the plugin needs to do is to check if the action is valid. Does the name already exists? If it exists, the action is not valid. The action can be done in the pre-validation. This is the most lightweight solution. There is no need to execute this logic within the database transaction. What is the benefit for this example? It is just a check.
If the action is valid (name is empty) and the process will continue, then all the normal validation, security checks will be done. I don't see any problems with that.
+1
Hi. PreValidation on Msdn is not guarantee in transaction. So I'd prefer doing on PreOperation.
Hi Anand,
In addition Andrew answer ,
Few things need to be considered .
As per MSDN the pre-validation stage occurs prior to security checks being performed to verify the calling or logged on user has correct permission to performed the intended operation.
Secondly pre-validation occurs outside database transactions.
Based on above two main criteria,, I would recommend to do this type of validation in the Pre-operation event instead of pre-validation. As because creation of account should be require the security check .
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (