For example, whether objects should be visible or not given certain conditions. Rules that govern visibility, perspectives and localization of objects in the model. The SummarizeBy property of columns is an example of such metadata. Rules that relate to metadata that alter the behaviour of client tools when browsing the model. Rules that relate to the way DAX formulas are written, for example to encourage the use of DIVIDE(,) instead of /. Use one of the following values for the Category of the rule: You may add Remarks to the rule to provide comments to the community regarding the behaviour and reasoning behind the rule, and also any limitations or exceptions. Critical / similar to 4, but guaranteed to cause issues such as deployment/processing errors or logical errors.Very important / similar to 3, but with a higher risk of causing issues.Important / may cause functional issues, performance degradation or end-user confusion.Minor importance / may cause end-user confusion or a less-than-optimal user experience.Rule Severity should be an integer between 1 and 5: Rule Description should contain a detailed developer-oriented description of the rule and suggestions on how to fix objects that are catched by the rule. Rule Name should be proper case and kept as short as possible, while still describing the essential function of the rule. Rule ID must be META_ALL_UPPERCASE_WITH_UNDERSCORES, and include the category prefix (see below). "ID": string, "Name": string, "Category": string, "Description": string, "Severity": int, "Scope": string, "Expression": string, "Fićxpression": string (optional), "Remarks": string (optional) Rules should be submitted in their JSON representation: If you have a question regarding how to use the Best Practice Analyzer or if you are missing some features of the Dynamic LINQ expression language, open a new issue on the main Tabular Editor repository.The community will evaluate whether the rule will make it into the set of recommended Best Practices. If you have already created a rule in Best Practice Analyzer, open a new issue and attach the JSON definition of your rule (see below). Someone from the community will then provide the Dynamic LINQ expression to use in the Best Practice Analyzer, so you can validate if the rule behaves as you expect. If you have an idea for a Best Practice Rule, open a new issue describing what you would like the rule to do.The community is encouraged to contribute rules to the collection of Best Practices published here. You should then see the rules show up in Best Practice Analyzer: %ProgramData%\TabularEditor to make the rules available for everyone on your local machine.%AppData%\.\Local\TabularEditor to make the rules available only for you.Store the file in one of the following locations: To use these rules, simply download the BPARules.json file from the releases page. This repository holds a recommended set of rules for the Best Practice Analyzer of Tabular Editor.
0 Comments
Leave a Reply. |