A nested exception is where a formula is performing an update on the CRM system & fails because the update triggered another business rule (e.g. formula, real-time workflow, custom plug-in etc.) to fire which ultimately failed.  In order to see this nested exception we need to enable a specific tracing level. 

Typically what you see in the North52 trace log is the following message with no further details, 

"Unhandled Exception: Microsoft.Xrm.Sdk.InvalidPluginExecutionException: An error has occurred in North52 FormulaManager."

List of the possible sources that a nested exception is being thrown,

  •  Another formula
  •  Real-time Workflows
  •  Custom Plug-In
  •  Data Integration such as Scribe, Simego, etc.

Capturing Nested Exceptions

In order to capture the nested exception we need to turn on tracing. The steps below will show you how to do this,

  • Navigate to the North52 Configuration record
  • Change the Tracing Level picklist to Information (Show Exception Details)
  • Click Save
  • Perform the action that caused the failure to see the nested exception details


Note 1 : 

After you perform a logging session always turn logging off

Note 2 :

 This tracing level does not create records in the N52 Trace entity. It just shows additional nested trace information as part of the standard trace download that Microsoft provide


Did you know?

We listen to customer feedback!

Although our business rules engine for Dynamics 365 has over 500 functions, sometimes you'll come across a requirement for which we don't provide a specific function for. Let us know the details and our team will be happy to review your requirement or suggestion and either provide a solution from our existing toolset or look to enhance our product to meet your requirements. 

You can make suggestions on our ideas page or email us directly at