CustomSync : Bypasses only synchronous plugins and real-time workflows.
To use this feature, the calling user must have the prvBypassCustomBusinessLogic privilege.
Using the BypassBusinessLogicExecution parameter, you can choose exactly what to skip: prvbypasscustombusinesslogic
By default, this privilege is typically granted to the role. If you are writing a script or integration service, the Application User or Service Account running the script must have a security role that includes this privilege. If the user lacks the privilege, the API call will ignore the header (and run the plugins) or fail, depending on the context.
If you have ever found yourself waiting hours for a simple data import to finish because it keeps triggering plugins that aren't relevant to that specific operation, you need to know about the BypassCustomBusinessLogic (often referred to as PRVBypassCustomBusinessLogic ) header. CustomSync : Bypasses only synchronous plugins and real-time
For a user creating a single account via the UI, this logic is vital. But for your migration script? It is a nightmare. The logic is unnecessary, it drastically slows down the import speed, and it might even fail due to API rate limits on the ERP side.
If you are testing , use these insights to build stronger workflows. If you are testing someone else’s application , always have explicit written permission. If you are writing a script or integration
You can bypass specific plugin steps by providing a comma-separated list of Step IDs using the BypassBusinessLogicExecutionStepIds parameter.
However, treat it like a surgical scalpel, not a sledgehammer. Use it to trim away unnecessary processing during migration, but never use it to bypass logic that protects the validity of your business data.
Associate the prvBypassCustomBusinessLogic privilege to a security role by using AddPrivilegesRoleRequest. C#. Copy. static void . Microsoft Learn
Historically, developers had to create complex workarounds, such as: