Best practice deviations

Finance and Operations/AX Developer Forum
1

Hello

I have a temporary table that has EDT-s in it. Those EDT-s have relations to other tables (say SalesTable) and I do not want to make relations under the table I am making. Thus the problem arises, that AX 2012 marks this as a BP Deviation (Example: “The relation under the extended data type (EDT) CurrencyCode must be migrated to a table relation. Consider using the EDT relation migration tool.”).

Why this is a problem?

We are using DFS as a version control system and we have enabled BP Deviation checking, so any code which has BP Deviation cannot be inserted into version control. Now we know that these temporary tables we are making CANNOT have these relations for various reasons and that it will NOT be a problem that these relations are missing, but we cannot just switch off the whole DFS version control BP Deviation control because of this…

What do I want to know?

  1. Can you make exceptions in DFS to allow temporary tables to ignore this particular BP Deviation?
  2. Can you document a BP Deviation somehow on this particular BP error?
2

If you want to understand the problem regarding relations, look at Migrating Extended Data Type Relations.

Nevertheless you can suppress the check by several means:

  1. Uncheck specific rule(s) in the Best practice parameters form.
  2. Add rules and objects to be skipped to SysBPCheckIgnore macro.
  3. If necessary, change the code of the rule (e.g. to add a parameter for Best practice parameters).

You’ll find details in the documentation: Best Practices Checks [AX 2012].