Comments (6)
Hi Marco. Just to clarify. Assume I have the following measures and dependencies:
and Detail Rows have been defined at the top-most measure [Reseller Total Sales].
Should the rule then output all measures that depend on [Reseller Total Sales] recursively, or just the measures that reference it directly? I guess in the former case, the rule could potentially output many measures that would be in violation of the rule, and it would not always be clear why, where as in the latter case, the rule would have to be re-evaluated continuously while new Detail Rows expressions are added...
from bestpracticerules.
Good point. I think that providing the warning at the first level is the right thing to do. However, we should figure out how to "disable" the warning for specific measures. I don't know whether we might use some annotation or some comment in the measure. For example, if it's ok that Total Sales doesn't provide the warning, I would like to mark Total Sales in some way, so that Reseller Current Quarter Sales still generates the warning (unless I disable that measure as well).
from bestpracticerules.
This is already possible today. In the screenshot below, you can see that I've already ignored the rule for the [Total Sales] measure (shown in the Property Grid). As you can see, an annotation has been added to the measure, specifying the ID's of the rules that should be ignored:
One more question: Should the rule ignore measures residing on a table that has a Default Detail Rows Expression defined?
from bestpracticerules.
Believe it or not, I missed the "Default Detail Rows Expression"!
Ok, I would do the following (but I'm very open to discuss it because I never spent too much time on this):
- a measure A residing in a table X that has "Default Detail Rows Expression" is like a measure that has "Detail Rows Expression" defined locally on the measure (with one exception)
- a measure B residing on table Y that depends on A should show the warning if "Detail Rows Expression" is not defined in B (regardless of the default in Y) --> however, for this case an "ignore rule on derived measures" applied to A could be useful.
- a measure B residing on table X that depends on A should show the warning if a specific "Detail Rows Expression" is defined in A (regardless of the default in X) - this is the exception to the first rule (do you see my point for this case?)
Feedback is welcome - we are in unexplored territories here.
from bestpracticerules.
I agree with your 3rd bullet, since we have to assume that, in general, if measure B depends on A, it must mean that B is a more "specialized" case of A. And so any "specialization" (in this case, Detail Row Expression different from the table default) that has been explicitly set on A, should also prompt us to consider doing something to B.
from bestpracticerules.
This is also my feeling. Not sure how it can be implemented, but it is a "nice to have" feature,
from bestpracticerules.
Related Issues (20)
- Translate display folders rule reports incorrect violations HOT 1
- [Rule Submit] Fix Disable Attribute Hierarchies HOT 4
- [Rule Submit] Disable auto time intelligence HOT 2
- [Rule request] Avoid sideways recursion HOT 1
- [Rule Request] To check if "Filter' is used to filter a column in a measure HOT 1
- [Bug] IsAvailableInMdx on columns used as SortBy
- Rule for Disabling auto date/time misspelled
- Rule question when using BPA in Tabular Editor by command line
- [Rule Request] Data type 'Any' must be changed HOT 1
- APPLY_FORMAT_STRING_MEASURES rule should exclude text measures
- [Rule Submit] Disable Attribute Hierarchies rule should not apply to columns referenced by PATH function
- Export/Compile BP Violations?
- Export/Compile Violation List HOT 1
- [Rule Request] Provide short rule description HOT 1
- [Rule Request] Hide foreign key columns HOT 1
- [Rule Request] Measure or Column not visible in any Perspective
- [Rule Request] Expressions with non fully qualified columns HOT 1
- [Rule Request] Per-Model Exceptions to BPA Rules HOT 1
- Unable to load or add own BPA rules file
- camelCase rule is causing false positives on PascalCasing HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bestpracticerules.