Improved filters for data security

In previous releases, the record-level security feature was used to help secure the
data. The filters that were used for record-level security could not be based on
fields that were contained in a separate table from the data that was being
filtered. For example, to filter sales lines, you could not use the customer
location, because the customer location field is not contained in the sales line
table. In addition, record-level security was enforced only through the client
interface.

In Microsoft Dynamics AX 2012, the extensible data security framework can be
used to help secure the data. By using the new framework, you can create data
security policies that are based on data that is contained in a different table. Data
security policies are enforced at the server, regardless of the type of client that is
used to access the data. In addition, policies can take security privileges into
account. For example, the administrator can grant View access to one subset of
sales orders and Edit access to another subset of sales orders.

CAUTION: The record-level security feature is still available in Microsoft
Dynamics AX 2012, but it will become obsolete in a future release. Filters that
you previously set up for record-level security can still be used. If you set up new
filters, we recommend that you create data security policies by using the
extensible data security framework.

Regards,
Hossein Karimi