Related column of a fact table - SSAS Tabular

Hi,
I'm developing a SSAS Tabular model using a SQL Server 2012 SP 1 installation.
For a fact table I've created some calculated columns using the DAX RELATED function. These columns not are hidden to client tools. When I deploy the project and I open an Excel workbook in order to connect the SSAS Tabular cube, in the field list I cannot
see the calculated columns by RELATED function.
For me, this in an issue and not a normal behaviour.
Any suggests to me, please? Many thanks

Hi Pscorca,
Generally, if we create a calculated column on SQL Server tabular model database on SSMS, and then go to Model-> Process -> Process All and finish the data processing. Then when we connect the database in EXCEL, the calculated column will appear on
the Excel. In your scenario, you cannot see the calculated columns. It’s strange behavior. However we cannot give you the detail reason for this issue base on the limited information.  Please refer to the link below which describe the detail steps about
create a calculated column, then check whether if you missing any step when creating calculated column.
Add Calculated Column and Measures to Tabular Model
If the issue persists, please elaborate your production environment and the steps to create the calculated column, so that we can make further analysis.
Regards,
Charlie Liao
TechNet Community Support

Similar Messages

  • No. of columns in a fact table

    What is the normal range for the number of columns in a fact table in a typical start schema/datawarehouse?
    Couple of 100 columns in each fact table...?
    Thank you

    Post Author: jsanzone
    CA Forum: WebIntelligence Reporting
    Suzie,
    You can create a new local variable to report (called something like "NVP"), leave it as a "Dimension" and in the formula type:
    if([col_a]=0 or [col_b]=0;"NO VALUE PRESENT")
    Basically, you are using the "if" function and the syntax is very much like used in excel except you separate the arguments with a semi-colon versus a comma.  You start out with "if()" and within the parenthesis is a logic statement followed by when true do this else that (with the "else that" portion optional as shown above).  The drawback to using a local variable is that every report you write must be customized with the local variable versus establishing this logic in a "case" statement when building the data mart and thus it becomes resident and usable like any other column of data in your database.  In some cases you are forced in using it as a local variable due to variations in the data and the logical outcome is not known until the very end of all computations, and at other times you can get away with embedding the logic at the time of constructing your data mart -- it all depends on how the data is used and sliced and diced.  Good luck and write back if you have any further questions.

  • Filter Date Table (SSAS Tabular)

    Hi Guys,
    I'll try to define my issue as clear as possible.
    Am creating a model for SSAS Tabular but I have following problem.
    I have a Date Table that I want to filter depending on what the user select from another table with values like:
    Today, Yesterday, This Week, Last Week, This Month, Last Month, .....
    What I have tried:
    (1) My Date table contains flags(columns) for each of these values. Filtering on these values is no problem. But then I have a long list of different possible flags.
    (2) I created a copy of my date table but with the flags unpivoted (DateId, FlagName, Value (0 or 1))
    I was hoping to be able to create somehow a relation between my date table and this table, but no success.
    Also this way I would have a field that users can filter on (choose what period they want to see)
    But sadly enough (2) did not work and I can not find any other way to find a solution for it.
    Any help would be great.
    Regards,
    Sammy

    In your date table, you can create different attribute for
    each condition below:
    1. Today, 2. Yesterday, 3. This Week, 4. Last Week, 5. This Month, 6. Last Month
    So, if we consider above attributes there will be 6 different attributes with "Yes/No" Or "True/ False" Or "1/0" whatever flag.
    I would suggest you to calculate these conditions in sql query which will be faster compared to calculated columns in the model.
    Unfortunately, tabular model 2012 do not support dynamic set so you cannot build a single attribute with these values @server side.
    I had similar question sometime back, check if you find something useful from this thread -
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/302dd796-2677-44df-a76e-b053dcd14117/ssas-tabular-model-dynamic-fiscal-period?forum=sqlanalysisservices
    If this post answers your query, please click "Mark As Answer" or "Vote as Helpful".

  • Issue with non calculated column in a fact table

    Hi All,
    With 3 facts(Fact1,Fact2,Fact3) and 2 Confirmed Dimensions my joins work fine in Criteria when I include All calculated columns from facts. If I try to include a non calculated column from Fact1(Which is a number Data type) Columns from Fact2 and Fact3 show Null values. I know it is not recommended to include dimension columns in fact , does OBIEE not support Number type non calculated columns as well? Is there any work around that I can bring in my non calculated column from Fact and still get results for other fact columns.Iam at 11.1.1.7 of OBIEE
    Let me know if Iam not clear.
    Your help is much Appreciated.
    Thanks,
    Vineela.

    i would like to add 2 fields into my fact tables - LOAD ID (populated by a sequence during each load) and LOAD DATE.
    as these fields are not related to any reporting dimensions, it is still possible to add them in OWB ? the fact wizard always ask for a foreign key to a dimension ...
    Duncan,
    If you want to add non dimensional attributes to a fact by using OWB, you can create additional measures to it and use them as attributes.
    Igor

  • Hide/show a column for some users in SSAS tabular

    Hi,
    I have a requirement to show one of the columns in a table only to some of the users. I know SSAS tabular only supports row level security. The only solution I came up with yet is to create two different models. Unfortunately this wastes a lot
    of expensive RAM in the server. Is there a better way? Some kind of work-around? ;)
    Best Regards
    Ulf

    One other way is to embed the security level into the table. You can do this by adding a "security_ID" into your structure and join it with a security table and join this to a security table which has a junction of Tablecolumns/User or TableColumns/UserGroups. 
    The next step is to use a Case When in your sql query  and make a decision to show null or real data for any column. 
    Business Intelligence Architect

  • How to create unique key column in ROLAP fact table?

    Hi all,
    Is there a way to create a single column primary key (or unique index) on my ROLAP cube (and fact tables) in OWB? if so, what I should do in my mappings?
    Thanks!
    - Andrew

    Have you all conformed dimensions between the two facts?

  • Constructing Calculated Measures in MDX for different measures using same columns in a fact table

    Hello,
    i have a fact table with 2 columns corresponding to dimensions Dim1, Dim2. In the same table i have 4 other columns Value_Type(int), INT_VALUE(int), FLOAT_VALUE(float), TEXT_VALUE(string). There are a number of measures which are identified by Value_Type and
    depending on their nature could be written in one of the 3 columns (INT_VALUE(int), FLOAT_VALUE(float), TEXT_VALUE(string)) Let's say Measure1 with Measure_Type=1 is age, 2 is account balance and 3 is Name for clarity. There could be other measure types that
    use these 3 same columns for data. So the sample fact table looks like this
    Dim1 Dim2 Measure_Type INT_VALUE FLOAT_VALUE TEXT_VALUE
    10 10 1 25
    10 10 2 2000,34
    10 10 3 John
    10 20 1 28
    10 20 2 3490,23
    10 20 3 Frank
    My task is to write an MDX query for each Dim1, Dim2 combination which returns all 3 measures in the same row. The idea is to construct a calculated member for each Measure that returns value from the right field. For example for Measure1 we take INT_VALUE
    with measure_type=1. The problem is i don't know how to construct MDX query for these calculated members. Can you please help me?
    So my final goal is to write an MDX query that returns all measures in one row for each set of Dim1, Dim2
    SELECT [Measure1], [Measure2], [Measure3] ON COLUMNS,
    NON EMPTY [Dim1].[Dim1].[Dim1].Members*[Dim2].[Dim2].[Dim2].Members ON ROWS
    FROM [Cube]
    Dim1 Dim2 Measure1 Measure2 Measure3
    10 10 25 2000,34 John
    10 20 28 3490,23 Frank

    Hi Kosmipt,
    I would combine the "INT_VALUE", "FLOAT_VALUE" and "TEXT_VALUE" columns into one with STRING data type for the fact table. And there should be one dimension to store the Measure_Type informations. Then in cube, you can write MDX scope for every one of
    "Measure_Type" dimension members. For example,
    scope(
                [Measures].[M]
        [DimMType].[MType].&[1]= CINT([Measures].[M]);                                                                                                                             
    end scope;
    Once the cube is built by the above way, you can write MDX like something like the following to achieve your purpose.
    WITH member [Measures].[Measure1] AS ([DimMType].[MType].&[1],[Measures].[M])
             member [Measures].[Measure2] AS ([DimMType].[MType].&[2],[Measures].[M])
             member [Measures].[Measure3] AS ([DimMType].[MType].&[3],[Measures].[M])
    thanks,
    Jerry

  • Multiple Date columns  in one fact table

    hi ,
    I have a fact which related to multi date, like bid date, win date, lost date ,etc...,
    I have create dimension like dim_bid_date, dim_win_date,
    but if I wan to create a report , the value sum by the month (2012.01-2012.08), I don't know how to do in one report which related multi date.
    I think I should have a 'common date', how to do, can anyone explain it in detail. thanks.

    2 thinks here, do you want to reports based on bid date,win date, lost date etc?
    if yes you need to create those many date logical tables and you need to have in Subject area (something like 'Agreement Details' subject area if you have OOB rpd)
    Coming to your report requirement 'sum by the month'; I dont think this is complete report requirement, you need to know month type like bid month or win month or lost month or what!!
    if user dont want do report by those mentioned dates then just use just date of type( bid,win etc) with out using day dim;
    you might have some date like created date, create report based on that for sum by the month.
    Hope this helps, if helps pls mark

  • Including column from fact table reduces number of rows returned

    Hello
    I am facing this issue where in a report I select 5 columns from a fact table. Out of these five columns one of the column is "Amount" for which the aggregation rule is defined as Sum in RPD.
    When I include these five column and filter results based on some criterion , I get all the rows (three rows) that satisfy the criterion. No I add a sixth column to my report and suddenly I only see one row returned by my report. Addition of this sixth column does not affect the criterion as the criterion is not based on this column. But this sixth column is a calculated column.
    I tried different things but because the report was just getting columns from one table (fact) and suddenly inclusion of one column leads to reduction in number of rows , I was unable to find any reason why would that happen.
    So I thought that some one in community may know that in what scenario this happens.
    Thanks

    Are there any repeated values? I'm wondering if what you're seeing is actually suppression of repetition in the results. Edit the analysis, go to the criteria tab, click column properties, go to the Column Format tab, and change the setting for value suppression from 'Suppress" to "Repeat". Repeat for each of your 6 columns and check the outcome.
    Otherwise, I would try testing with other calculations and also bring in some columns from dimension tables to see how this affects the result. You should be able to come up with a case-by-case scenario to work out exactly what causes the rows to be suppressed which will get us one step to closer to working out why the rows get suppressed.
    Thanks,
    George

  • Users selecting "All Choices" on columns in fact table

    We have a dimensionalised data structure in our Oracle DW and the fact table contains 750million rows. I'm finding the users are selecting a column in the fact table to filter on, and selecting the "All Choices" option. This then runs an SQL like:
    select distinct(column_name) from column_table
    Which kills the DW server.
    Does anyone know of a way of stopping this? to only allow the All Choices option on one of the dimension tables?
    Oracle 11g
    BI 10.1.3.4.1
    both on Redhat LINUX
    Thanks in advance.

    Thanks to all for advice/suggestions. In the end I resolved this ( rather a brute force method ) by hacking adjusting one of the XML message documents, standardviewtemplates.xml, that I'd copied into the customMessages directory.
    Its a real shame as it removes that function for all users on every table, but some users keep selecting the "All Choices" option even after being told not to.

  • Link fact tables?

    hi all,
    I have two fact tables – charges and payments and both these fact tables are in the cube (as measure groups). On the relational side, these two fact tables are “linked” by a column called trans_no. Linking these two tables could be little tricky because
    a single charge can have multiple payments.
     for example, let’s say there was a charge of 100$ but the payment was done in two installments so there is one row in the charge fact table, but 2 rows in the payment fact table – both rows have the same transaction number but different date.
    It is also possible to have two charges in the charge fact table with the same transaction number but one payment in the payment fact table. So I think this is a many-to-many relationship.
    How can I link these tables in SSAS? I would to be able to show payments and charges side by side down to the transaction level. Please advise and thanks for the help.

    thank you Ken, so i am going to have  dimensions then? -
    1. off of payments
    2. off of charges
    3. "Transaction" dimension
    The reason i am saying i need #1 and #2 is because i need some other attributes such as "transaction type"(void etc) from both the fact tables. does this sound correct? i feel like i am cluttering the cube :(

  • Issue using one 2 Fact tables with one dimension Table.

    Hi,
    I have 1 Dimension table X and 2 Fact tables A and B
    X is joined to Both A and B for Loan Amount ( with A) and for colleatral amount (with B) when I am selecting the X.Product_Name, A.Loan_Amt, B.Collateral Amount, it is giving an error message
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table EIP Collateral FACT) does not contain mapping for [EIP Reporting FACT.PD ID]. (HY000)
    Any clues???
    Is there a Inner or Outer join which needs to be created or set in the RPD to get the desired results???

    Ok..
    I have one table which is Porfolio Details which has Portfolio name, Product Category , Product Name, Product ID, Product sources code.- This is my Dimension table.
    I have another 2 set of fact tables : EIP Reporting FACT and EIP Collateral FACT..
    These two tables are joined to Portfolio Details table.
    EIP Reprting FACT gives portfolio wise Loan Amount
    and EIP Collateral FACT gives Portfolio wise Collateral Amount details for same set of customer..
    Now, I am selecting Portfolio Name, Product Category, Product Name,SUM( EIP Reporting FACT.LOAN_AMOUNT), SUM(EIP Collaetral FACT.Collateral_Amt) in a report
    Now, on selecting these columns I am getting that error message which is related to mapping.
    If I take any column from Portfolio details table and any column from EIP Reporting FACT- It works.
    If I take any column from Portfolio details table and any column from EIP Colletral FACT- It works.
    But if I take any column from portfolio table and columns from both FACT tables it gives mapping error...
    Hope I am able to explain the issue in a better way now..
    Edited by: help-required on Mar 11, 2010 6:53 PM
    Edited by: help-required on Mar 11, 2010 6:53 PM

  • Reg: Fact table and Dimension table in Data Warehousing -

    Hi Experts,
    I'm not exactly getting the difference between the criteria which decide how to create a Fact table and Dimension table.
    This link http://stackoverflow.com/questions/9362854/database-fact-table-and-dimension-table states :
    Fact table contains data that can be aggregate.
    Measures are aggregated data expressions (e. Sum of costs, Count of calls, ...)
    Dimension contains data that is use to generate groups and filters.
    This's fine but how does one decide which columns to consider for Fact table and which columns for Dimension table?
    Any help is much appreciated.
    Pardon me if this's not the correct place for this question. My first question in the new forum.
    Thanks and Regards,
    Ranit Biswas

    ranitB wrote:
    But my main doubt was - what is the criteria to differentiate between columns for Fact tables and Dimension tables? How can one decide upon the design?
    Columns of a fact table will often be 'scalar' attributes of the 'fact' data item. A dimension table will often be 'compound' attributes of a 'fact'.
    Consider employee information. The EMPLOYEE table can be a fact table. It might have scalar attribute columns such as: DATE_HIRED, STATUS, EMPLOYEE_ID, and so on.
    Other related information that can't be specified as a single attribute value would often be stored in a 'dimension' table: ADDRESS, PHONE_NUMBER.
    Each address requires several columns to define it: ADDRESS1, ADDRESS2, CITY, STATE, ZIP, COUNTRY. And an employee might have several addresses: WORK_ADDRESS, HOME_ADDRESS. That address info would be stored in a 'dimension' table and only the primary key value of the address record would be stored in the EMPLOYEE 'fact' table.
    Same with PHONE_NUMBER. Several columns are required to define a phone number and each employee might have several of them. The dimension tables are used to help 'normalize' the data in the employee 'fact' table.
    And that EMPLOYEE table might also be a DIMENSION table for other FACT tables. A DEVELOPER table might have an EMPLOYEE_ID column with a value that points to a 'dimension' row in the EMPLOYEE dimension table.

  • How do you handle update and delete rules for fact tables?

    I have a fact table with a composite key of 5 columns. Two of the columns are FKs to the date dimension. I was setting the delete/update rules for the FK relationship in SSMS and it had a problem with me creating cascade action on the FKs that connected
    to the date dimension.
    What is the proper way to set up FK relationships in fact tables with SSMS when  you have composite keys as most fact tables do?

    Yeah I understand all that. What I'm trying to do is to protect my database from RI violations that occur by production support people blowing away stuff in a dimension table but forgetting to blow away related records in the fact table. I want those fact
    records deleted automatically so we don't have orphan records which was a real issue at a previous engagement. Production support is usually just people that know SQL and some relational modeling. It's not too likely they will understand the details of dimensional
    modeling enough such that they would know that they had to blow away the fact record first.
    My problem is I have a FK to a role playing dimension (the date dimension in this case). So basically I have to columns in the fact table that have a FK relationship to the PK of the date dimension. When I create both relationships SSMS and try to have both
    of them cascade delete SSMS has an issue with it.
    The error I get is:
    Unable to create relationship '[relationship name]'
    Introducing Foreign Key constraint '[constraint name]' on table '[table name]' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other foreign key constraints.
    I can go ahead and put no action and the table will save fine. The question now becomes how does the cascade delete actually work. Can I just set one part of the key to cascade delete?
    Actually I just realized that this is an even bigger design issue. What DOES happen to a fact record when one of it's dimensions gets deleted and I've got full RI set up on the table?
    Or am I totally thinking about this wrong. Do you set up cascade deletes in a dimensional model? Is there a way to prevent deletes from the dimension table if there are related fact records?

  • How to display a description in fact table from an unrelated DIM table in powerpivot?

    Hello,
    I have two tables in powerpivot 2010: 1 that is my fact and the is unrelated. I'm relatively new to SQL and powerpivot.
    What I need to do is display a description from my DIM table based on a column in my fact. Is this possible? In my fact, I
    have  a ReasonID, the DIM has the ReasonID and description. I just need the description added in my fact as a new /
    another column. Thanks. John

    Hello,
    When you have the same column in both tables, then they are related, even if in database no primary / foreign key is defined. In PowerPivot we can define additional / manual relation, just Change to "Diagram View" and define the relation like below:
    But if you still want the "Dim description" as a computed column in your fact table, then you can use the
    LOOKUPVALUE function
    =LOOKUPVALUE(Dim01[Description], Dim01[ReasonId], Fact01[ReasonId])
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

Maybe you are looking for