Analysis Services Tabular Model - New Calculated Table (with DAX) grouping by Weeks
I am creating an AS Tabular Model in VS2017.
I imported the table I needed from a SQL DB server by creating an expression with the next structure:
SELECT ...
FROM ...
WHERE ...
GROUPBY ...
The table has a DATE column.
In my AS Tabular Model I would like to create a calculated table (using DAX) with the same columns but this time grouping by week, so all the totals are summarized.
How can I achieve this?
I'll like to avoid creating another expression for this as I am trying to optimize the report I already created by directly querying the SQL DB.
Thanks in advance.
sql visual-studio-2017 expression dax analysisservices
New contributor
add a comment |
I am creating an AS Tabular Model in VS2017.
I imported the table I needed from a SQL DB server by creating an expression with the next structure:
SELECT ...
FROM ...
WHERE ...
GROUPBY ...
The table has a DATE column.
In my AS Tabular Model I would like to create a calculated table (using DAX) with the same columns but this time grouping by week, so all the totals are summarized.
How can I achieve this?
I'll like to avoid creating another expression for this as I am trying to optimize the report I already created by directly querying the SQL DB.
Thanks in advance.
sql visual-studio-2017 expression dax analysisservices
New contributor
The usual approach is to create a calendar table with a week attribute, create a relationship to your table. Then allow analysis services to do a summary by on the fly when you tell it to (by selecting week in your client tool). Then if performance is not acceptable you might want to consider pre creating a summary table. In other words.. analysis services already does this on the fly and you don't usually need to specifically create a summary table. Summary tables make things kinda complicated because users have to know which is the right able to use
– Nick.McDermaid
6 hours ago
add a comment |
I am creating an AS Tabular Model in VS2017.
I imported the table I needed from a SQL DB server by creating an expression with the next structure:
SELECT ...
FROM ...
WHERE ...
GROUPBY ...
The table has a DATE column.
In my AS Tabular Model I would like to create a calculated table (using DAX) with the same columns but this time grouping by week, so all the totals are summarized.
How can I achieve this?
I'll like to avoid creating another expression for this as I am trying to optimize the report I already created by directly querying the SQL DB.
Thanks in advance.
sql visual-studio-2017 expression dax analysisservices
New contributor
I am creating an AS Tabular Model in VS2017.
I imported the table I needed from a SQL DB server by creating an expression with the next structure:
SELECT ...
FROM ...
WHERE ...
GROUPBY ...
The table has a DATE column.
In my AS Tabular Model I would like to create a calculated table (using DAX) with the same columns but this time grouping by week, so all the totals are summarized.
How can I achieve this?
I'll like to avoid creating another expression for this as I am trying to optimize the report I already created by directly querying the SQL DB.
Thanks in advance.
sql visual-studio-2017 expression dax analysisservices
sql visual-studio-2017 expression dax analysisservices
New contributor
New contributor
edited 7 hours ago
gameon67
19212
19212
New contributor
asked 9 hours ago
Cassandra PrattCassandra Pratt
63
63
New contributor
New contributor
The usual approach is to create a calendar table with a week attribute, create a relationship to your table. Then allow analysis services to do a summary by on the fly when you tell it to (by selecting week in your client tool). Then if performance is not acceptable you might want to consider pre creating a summary table. In other words.. analysis services already does this on the fly and you don't usually need to specifically create a summary table. Summary tables make things kinda complicated because users have to know which is the right able to use
– Nick.McDermaid
6 hours ago
add a comment |
The usual approach is to create a calendar table with a week attribute, create a relationship to your table. Then allow analysis services to do a summary by on the fly when you tell it to (by selecting week in your client tool). Then if performance is not acceptable you might want to consider pre creating a summary table. In other words.. analysis services already does this on the fly and you don't usually need to specifically create a summary table. Summary tables make things kinda complicated because users have to know which is the right able to use
– Nick.McDermaid
6 hours ago
The usual approach is to create a calendar table with a week attribute, create a relationship to your table. Then allow analysis services to do a summary by on the fly when you tell it to (by selecting week in your client tool). Then if performance is not acceptable you might want to consider pre creating a summary table. In other words.. analysis services already does this on the fly and you don't usually need to specifically create a summary table. Summary tables make things kinda complicated because users have to know which is the right able to use
– Nick.McDermaid
6 hours ago
The usual approach is to create a calendar table with a week attribute, create a relationship to your table. Then allow analysis services to do a summary by on the fly when you tell it to (by selecting week in your client tool). Then if performance is not acceptable you might want to consider pre creating a summary table. In other words.. analysis services already does this on the fly and you don't usually need to specifically create a summary table. Summary tables make things kinda complicated because users have to know which is the right able to use
– Nick.McDermaid
6 hours ago
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Cassandra Pratt is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54248036%2fanalysis-services-tabular-model-new-calculated-table-with-dax-grouping-by-we%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Cassandra Pratt is a new contributor. Be nice, and check out our Code of Conduct.
Cassandra Pratt is a new contributor. Be nice, and check out our Code of Conduct.
Cassandra Pratt is a new contributor. Be nice, and check out our Code of Conduct.
Cassandra Pratt is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54248036%2fanalysis-services-tabular-model-new-calculated-table-with-dax-grouping-by-we%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The usual approach is to create a calendar table with a week attribute, create a relationship to your table. Then allow analysis services to do a summary by on the fly when you tell it to (by selecting week in your client tool). Then if performance is not acceptable you might want to consider pre creating a summary table. In other words.. analysis services already does this on the fly and you don't usually need to specifically create a summary table. Summary tables make things kinda complicated because users have to know which is the right able to use
– Nick.McDermaid
6 hours ago