Develop > Tailoring > Form creation > Dynamic View Dependencies > Using Dynamic View Dependencies vs. Data Policy

Using Dynamic View Dependencies vs. Data Policy

Overuse of DVD on forms can result in performance problems. For example:

  • Using the select function or a $ variable that is not on the form requires an interaction with the server. On connections with slow network response the use of these types of DVD statements can significantly impact performance.
  • Using Focus In/Out or Data Changed Events also causes a server interaction. During design, the response time may seem adequate. However on a network with a half second response, it can be cumbersome.

Data Policy operates at the table level and achieves many of the same results without the complexity and without taxing system resources. For example, one common use of DVD is to set Visible or Readonly conditions, both of which can be set using Data Policy. With Data Policy, the conditions are evaluated on the server before the form is sent, thus avoiding a network interaction.

Related concepts

Dynamic View Dependencies
Field comparisons
Field value matching
Dynamic functions

Related tasks

Use field comparisons
Use dynamic functions
Use field value matching