• Do users need any special permission or role for Dynamic Forms?
    To create or update rules the user must have the System Administrator role. No permission or role is needed by other users for Dynamic Form rules to work. Dynamic Forms will not override the security permissions set up for each user.

  • How do I know if a rule is working?
    Any rule that is published is active for all users of the organization. To confirm that the rule is working as expected, we recommend that you test the rule once published, just as you test all other changes made to your Microsoft Dynamics CRM organization.

  • Why are my rules still executing when I deleted the Dynamic Forms Solution?
    Once published, the rule is applied to the entity and is not removed when you delete the Dynamic Forms Solution. You must delete each rule, which removes the rule from the entity before deleting the Dynamic Forms Solution.

  • If there are conflicting rules, which rule is adhered to?
    Rules are processed in the order in which they appear in the Dynamic Forms configuration page; therefore if two rules conflict, the rule listed last would win. Rule order can be changed by dragging and dropping the order of rules in the Dynamic Forms configuration.

  • Can Dynamic Forms be used to secure a form component?
    Dynamic Forms should not be used to try to administer security of any kind. For example, even if a Dynamic Form rule hides a field on a form, it will still be accessible via printing, Advanced Find, Views, etc.

  • I created a rule using the “Show” Action. Why doesn’t it seem to be working?
    Showing a field, section, tab, etc relies on that component being Not Visible by Default on the Form. Check to ensure that the Visible by Default box is unchecked for that component’s properties.

  • Performance seems slow when “Hiding” a large number of fields. What can I do?
    Choosing to hide many fields with a Dynamic Form rule may cause slow performance and a poor user experience because fields seem display and then disappear from the form. Instead of hiding a large number of fields, consider making the fields not visible by default, and then “Showing” them with the Dynamic Forms rule. This makes the fields seem to appear, which provides a much better user experience.

  • How do I migrate rules from Development to QA/Production?

    To migrate Dynamic Form rules you do NOT need to install the Dynamic Forms Managed Solution in each of your Orgs. It is best practice to only install Dynamic Forms in your Development Org, and promote your changes to QA and Production.

    Dynamic Forms is a GUI for creating JavaScript Web Resources that control your rules. This Web Resource file must be included in your solution for each entity that you are migrating from Development to QA or Production. The Web Resource can be identified by the naming convention sonoma_/df/entityname.js (Ex: sonoma_/df/account.js)

    **Importing the solution without the Dynamic Forms Web Resource files may cause an import failure if the Web Resources don’t already exist in the target Org. Failure will not occur if the Web Resources exist, however the Dynamic Form rules will not be updated in the target Org.**

  • What do I do if I want the full version of Dynamic Forms to be able to create as many rules as I want?
    Please fill out the Contact Us form.