microsoft / microsoft/Analysis-Services
Assistance needed on "Calculated Tables" rule
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 732
- Forks
- 433
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
For this rule 'Reduce usage of calculated tables", is there a way we can by pass Field Parameter tables? Right not it considers field parameters as calculated tables.
Also is there a way I can set a limit, like only display this as violation if the number of calculated tables in the dataset is greater than 3?
Looking for some suggestions. Thank you.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names the “Reduce usage of calculated tables” rule and includes a screenshot, but no file, test, or entry point. Start by locating that rule and determining how field parameter tables are identified, then clarify whether a configurable violation threshold is in scope. Done requires agreed behavior for both requested cases and corresponding tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100