In this scenario, we want to hide/show the Credit Limit field depending on the value of our Credit Hold field. 

However this Credit Limit field is in the Header section of our form. 

We do this by adding the prefix "header_" to the field schema name in the appropriate function.

Note: the Credit Limit field will need to be in the header of the form.

North52 BPA Solution

The North52 BPA solution works like this:

  • A formula is created that will trigger whenever the field Credit Hold is changed on the Account entity or whenever an Account form is loaded
  • The formula will check to see what the Credit Hold field is set to
  • If Credit Hold is set to Yes, the formula will hide the Credit Limit field
  • If Credit Hold is set to No, the formula will show the Credit Limit field

Setup Formula

  • Navigate to Settings > N52 Formula
  • Create a new formula, setting the following values in the Formula Guide:
    • Source Entity set to Account
    • Set Formula Type to Clientside - Perform Action
    • Set Event to Create & Update
    • Select the Decision Table Editor
  • Change the Name of the formula to Hide/Show Header field
  • Expand Source & Target 
  • In Source Property ctrl-click OnLoad and Credit Hold under the form Account for interactive experience Events
  • On the Decision Table editor, select cell A2
  • Select the Source Tab
  • Search for Credit Hold
  • Expand Source and click on Credit Hold {Value}
  • Select cell A4
  • Expand the Credit Hold {Value} node and click on Yes
  • Select cell B4 and enter the following:
  • Select cell B5 and enter the following:
  • Click Save
  • From the form Command Bar select N52 Commands > Publish Formula 

Note: you will need to ensure the field credit limit is on the header on the Account form for this to work. 


You are now ready to test. To test the formula, go to an Account record and change the Credit Hold field to see the Credit Limit field hide/appear

Did you know?

North52 Quick Buttons can be used on Dynamics Portals Entity Forms

That's right, you can trigger complex business rules via a button on an Entity Form. You could:

  • Retrieve information from another entity or even another system and return it to the form
  • Create or Update records on the button click
  • Process advanced decision logic from information that has been completed on the form but not submitted
  • Have dynamic buttons showing different options dependent on your business rules
  • And much more!

Learn more about North52 Quick Buttons for Dynamics Portals