Filtering by member properties

Hi,
I built a input schedule and i want filtering members by properties. I tried from the member lookup from the Current View, clicking in the dimension. I select the property value, flag the mark "use the filter" and i press "refresh". Well i've the members who fulfil this property. But what should i do if i want show only these members in my input schedule. Because if i've an expansion with "member set" = self or members it ignores the filter and show me the self member or all the members.
Thanx in advance.

Jose,
I hope I understand your question correctly.
You may concatenate the filter of the memberset; let me give you an example:
in the memberset you may create a formula like:
="type="""&A50&""""
than in cell a50 an enduser can enter an F or H or G (you have to unlock cell a50)
you could also create a nice dropdown box where an enduser can select F/H/G en link that to cell a50.
Hope this helps,
Alwin

Similar Messages

  • BPC 7.5 - Member properties disabled (grey marked)

    Since the upgrade to BPC 7.5 some of the member properties are greyed (disabled).
    Is it possible to change this setting somewhere?

    Hello Martin,
    now it's clear your question. The greyed properties don't have the check on the InApp properties of the dimension, so they aren't available in the OLAP and you can't use they in MDX functions or instructions.
    If you need some of these properties on the OLAP you must go on admin console\modify dimension, check "modify dimension property" on step 2, click on step 3 and check the InApp for these properties, so they will be black.
    Kind regards
    Roberto
    Edited by: Roberto Vidotti on Jan 31, 2012 12:06 PM

  • Repeated Header Row within a Details Section Only of a Group Ignores Tablix Member Properties

    Ok.  I have a situation where I have a details section of a group, and I am trying to get it to repeat the row headers on each page.  It's not working.  I've gone into Advanced Mode, and addressed the static Tablix Member for the left-most
    field of the header row in question, set the properties for the Tablix Member to "RepeatOnNewPage:  True" and "KeepWithGroup: After", and still, it refuses to repeat the row header for these details.  I've tried rebuilding and
    not deleting the column where the grouping was originally assigned (without deleting the grouping, of course), and assigned the properties for "RepeatOnNewPage" to that left-most, grouping field, yet I get the exact same results.  I've looked
    up solutions, and even spoken to the expert of experts, but no joy here.  I'm using VS'10.

    OK.  So it is fixed... sort of...
    Apparently, you must select to add group headers repeated as you create the group (inc. child group), BESIDES changing in Advanced Mode, Tablix Member /Properties / etc.   Then you have to format that extra column within your Tablix to
    make it appear to 'disappear'.  BUT EVEN THEN, there is a new problem:
    The headers will repeat on the additional pages, but only to a point.  For some odd reason, SSRS doesn't consistently render the repeated headers of the group details for
    every page, just where it is a hard (page) break, as opposed to a soft (page) break.  My gut tells me that this has nothing to do with the .xml code, but is an SSRS idiosyncrasy. 

  • MDX get member properties

    Context: SSAS 2005.
    How to get a property of a member? Is it member.property? I have seen member.properties() . When to use member.property and when to use member.properties()? I thought they are interchangeable then found they are not. E.g. Q1 and Q2 return the same result.
    Q3 works but Q4 won't compile. Can someone explain this?
    Q1:
    with member [measures].parentname as
    [Product].[Product Categories].CurrentMember.Parent.PROPERTIES("name")
    select 
    [measures].parentname  on 0,
    [Product].[Product Categories].[SubCategory].members on 1
    from [Adventure Works]
    Q2:
    with member [measures].parentname as
    [Product].[Product Categories].CurrentMember.Parent.name
    select 
    [measures].parentname  on 0,
    [Product].[Product Categories].[SubCategory].members on 1
    from [Adventure Works]
    Q3: 
    with member [measures].parentKey as
    [Product].[Product Categories].CurrentMember.Parent.PROPERTIES("KEY")
    select 
    [measures].parentKey  on 0,
    [Product].[Product Categories].[SubCategory].members on 1
    from [Adventure Works]
    Q4:
    with member [measures].parentKey as
    [Product].[Product Categories].CurrentMember.Parent.KEY
    select 
    [measures].parentKey  on 0,
    [Product].[Product Categories].[SubCategory].members on 1
    from [Adventure Works]

    I'm not 100% clear on the difference, as I recall properties() returns a string and .property can return another datatype.. this is just from memory.  Why don't you try MEMBER_KEY for q4... did you look at the list of member properties?
    -Ken

  • Difference between Name columns, Attributes, and Member properties

    I am studying for the "70-463 Implementing a Data Warehouse with Microsoft SQL Server 2012" exam. I am using the "Training Kit (Exam 70-463): Implementing a Data Warehouse with Microsoft SQL Server 2012".
    In chapter 1 of this book the different columns of dimension are explained., however I fail to understand the difference between the following column types:
    - Name columns: Used for human names of entities
    - Attributes: Used for pivoting in analyses
    - Member properties: Used for labels in a report
    As far I can understand all those three are labels and can be used interchangeable. Am I correct? Or am I wrong? I suppose there might be some practical differences, but how can you tell?
    I would really appreciate some examples showing the same data in a LOB
    (OLTP), data warehouse (star schema), and data mart (OLAP cube) form.
    Thank in advance.

    If I understand correctly the difference is about context or how you use the column.
    I did some further reading, and now I understand that an attribute can consists multiple columns. This way the following is possible:
    An attribute can be combined of multiple columns: e.g. the attribute address can combined by the apartment number, house number, street name, ZIP code, city, state, and country.
    An attribute can be column which is also part of another attribute: e.g. apartment number, house number, street name, ZIP code, city, state, and country can all be attributes own their own and simultaneously be part of the address attribute. The difference
    is the context which depends on business needs and technical requirements.
    An attribute can also consists of multiple columns which are aliases. This can be needed to support multiple languages or allow user friendly names (which allows spaces and funny characters) to coexist with technical names (which use a more restricted naming
    convention and typically use camel case.) Another example would be an additional column for abbreviations which might be needed for narrow column headers. Depending on the context a specific column can be used.

  • Filtering on member names using a wildcard

    Hello Olap World,We have an outline dimension based on a slow-varying dimension. Over time a member that exists under one parent may also need to exist under another. For example:WW EM CNTL HU AP CNTL HUIn order to have unique member names, I can suffix CNTL (for example) with its parent name - easy enough to do thru EIS.WW EM CNTL_EM HU_CNTL_EM AP CNTL_AP HU_CNTL_APWe also need to filter on these member names. Is there a way to use a wildcard in the filter so that I can build a read filter on all wildcard hits PLUS their descendents.I'd like to do @IDESC(@MATCH(WW,"CNTL*")) and pick up CNTL_EM and all its children and CNTL_AP and all its children. But alas, that syntax isn't supported (per my testing). Any ideas of how else to do this?Thanks!

    No, but you can apply filters using a UDA ... maybe this would work for you.

  • Setting member properties through Build rule.

    I have a hierarchy where the product structure needs to be updated.
    Now, I also need to add three different UDAs to each member.. and make some members Never share. (All in build rule)
    Please suggest me with any solutions.
    TIA,
    KRIS.

    To set the data storage you need to set the column field type to property in the rule file and then the value in the record to set to datastorage to "Never Share" will be N
    A list of properties are available at :- http://download.oracle.com/docs/cd/E17236_01/epm.1112/esb_dbag/dotrules.html#dotrules_2
    Also there is detailed information about building load rules
    You would set the column to UDA field type for UDAs
    An example parent/child build to set a member to "Never Share" and set UDAs would be
    Parent,Child,Datastorage,UDA1,UDA2
    Prod,ProdA,N,UDAName1,UDAName2
    Your load rule for a parent/child build would look something like
    PARENT0,Product Child0,Product Property0,Product UDA0,Product UDA0,Product
    Prod ProdA N UDAName1 UDAName2
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Input schedule: Derive key for key range from Dimension member properties

    Hey guys,
    I'm facing the problem within a input layout. There are three keys in the row key range.
    The first row key is filled by the members of a dimension. The second and third row
    should be filled by the dependencies shown in the dimension members.
    Example:
    Dimension:
    - Order number
    Properties:
    - Client (also implemented as standalone dimension where all required characteristics are maintaned)
    - Costcenter (also implemented as standalone dimension where all required characteristics are maintaned)
    Entries in dimension members of Ordern number:
    Order number, Client, Costcenter:
    1000, 10, 511
    2000, 10, 533
    3000, 12, 511
    4000, 15, 588
    Entries in dimension Members of Client:
    10,11,12,13,14,15,16,17,18,19,20
    Entries in dimension Members of Costcenter:
    511,533,555,588
    My row key range is defined as follows: Exp1: Order number, Exp2: Client, Exp3: Costcenter
    For Planning purposes i need a input schedule that schows only the valid combinations shown above
    in master data of order number. Is this possible or do I have to leverage script logic to use dependencies shown in master data for reporting oder planning purposes !
    Cheers,
    Moritz

    Hi Moritz,
    As Nilanjan said, this is not really possible with a basic EVDRE at the moment. Your best bet is probably to either build your own solution using EVEXP, EVGET, and EVSND, or to use an EVDRE based on only the Order # to get the values and an EVSND based on the Order # and the properties of the Order # in the AfterRange of the EVDRE.
    I actually like the second option a lot better (EVDRE with EVSND in the AfterRange) because for larger queries the read performance should be better and it will be more maintainable in the long run.
    Ethan

  • BPC validation rules based on member properties

    Hi all,
    validation rules seem to be very helpful in BPC NW but all examples I have found use members to define the rules. Is possible to use a member property to define a rule?
    For example, my ENTITY dimension has a STATUS property. I want to ensure that the user cannot save data when this property is equal to "CLOSED".
    thanks for your help,
    Alex

    Hi,
    You can acheive this by using Use BADI implementation under Validation maintenance.
    hope it helps...
    regards,
    Raju

  • Updating multiple member properties

    Hi,
    I am trying to update the account type property for multiple members by importing a modified ads file but i receive this warning after i deploy the application
    The 'PropertyArray' section contains a duplicate entry; the subsequent input line 'Alias|default|Cost of Removal Clearing.' will not be processed.
    using EPM version 11.1.1.3
    Appreciate any help
    Regards

    Got it.. it has to be looped..
    Thanks anyway for looking this. :)

  • Understand OlapQueryLog Dataset

    Hi everybody,
    I would like to create manuals aggregations to improve some MDX requests. (in SSRS Reports)
    When I'm reading OlapQueryLog table, i see this Dataset:
    10000011001000000,00000000000000000000....
    1000002300400....
    The first dimension is a time dimension with these selected attributes:
    Days
    Months
    Trimester
    Year
    => All Attributes is designed like hierarchy into "Attribute Relationships" of the "Time dimension"
    I create aggregation with "Day attribute" and it improve performance but not enough to speed up my request.
    I create 3 another aggregations : One on "Day attribute", one on "Month", one on "Year" => Nothing change
    I create another one with "Days", "Months", "Trimester" and "Year" (I don't worry about the BIDS warning on the unvalidated Aggregation) => Nothing change
    My questions:
    How to improve performance for this example of dataset?
    Thanks all for your responses.
    Arnaud

    Hi Arnaud,
    According to your description, you want to improve the performance of your MDX query for the SQL Server Reporting Services report dataset, right? In your scenario, since we didn't know the MDX query and the detail cube structure, it's hard to give you the
    detail measure to improve the MDX performance. Here are some useful tips to improve the performance.
    Remove empty tuples from your result set to reduce the time spent by the query execution engine serializing the result set.
    Use EXISTS rather than filtering on member properties to avoid a slow execution path.
    Filter a set before using it in a crossjoin to reduce the cube space before performing the crossjoin.
    Use Non_Empty_Behavior where possible to enable the query execution engine to use bulk evaluation mode.
    Reference:
    Top 3 Simplest Ways To Improve Your MDX Query
    Ways of Improving MDX Performance and Improvements with MDX in Katmai (SQL 2008)
    Regards,
    Charlie Liao
    TechNet Community Support

  • Returning only searchable properties

    I wanted to create an instance of the unified tree control such that I could present a collection of properties that are currently marked as being searchable.
    Is this possible with the unified tree control? When I try to create a "properties to be searched" tree in order to build a custom search query, I get back properties that are not necessarily marked as being searchable, causing a search query to bomb.
    I was using ClassID 36 (Property ObjectClass ID).
    I really don't want to have to reroll my own control if there's an easy way of filtering out those properties that aren't marked as searchable within the control.
    Thanks,
    Ari Braginsky
    ===
    <pt:standard.tree
    value="Select property"
    class="gContentSection"
    pt:windowname="myWindow"
    pt:windowfeatures="location=no,menubar=no,height=500,width=300"
    pt:RootID="1"
    pt:Multi="false"
    pt:SelectMd="2"
    pt:SubmitMd="2"
    pt:Submit="PickerSubmit"
    pt:Title="Property"
    pt:SubTitle="Pick a property"
    pt:Class="36"
    />

    My recommendation would be to subclass pt:standard.tree (com.plumtree.taglib.standard.TreeTag) and mix in this functionality. It shouldn't be quite as hard as rolling your own tag . . . .
    HTH,
    Chris Bucchere | bdg | [email protected] | http://www.bdg-online.com

  • Selecting Member Name and also Alias in Web Analysis report

    I have made a web analysis report and now i want to show member names as well as alias of the members which i have selected on row side. How can i do that?
    Thanks in advance.

    in the member properties, you have an option to show alias, member name, or both. Click on both / alias as per the requirement

  • How to Assign a Constant Value to a Dim. Member when pulling Master Data?

    BPC Gurus:
    I am trying load Vendor and Customer Master data into BPC dimension.  My Dimesnion has memebrs: ID, EVDESCRIPTION, PARENTH1, TYPE.  I have successfully pulled the ID and the description from 0CUSTOMER and 0VENDOR.  However, I
    need to have a ttext value for 'PARENTH1' and 'TYPE'.  For Customers, I want to add a FIXED value "'CUSTOMER' for every
    Customer ID pulled in and also for "TYPE", I want a value of "CUSTOMER".  When I maintainthe Dimension, I want to see
    th followingvalues:
    ID                          EVDESCRIPTION                                   PARENTH1                         TYPE
    0000000001         WALMART                                            CUSTOMER                        CUSTOMER
    0000000002          TARGET                                               CUSTOMER                        CUSTOMER
    and so ON
    Since we have Vendor Numbers in the same Diemsnion, when I pull Vendors, I need to have similar values as:
    ID                          EVDESCRIPTION                                   PARENTH1                         TYPE
    0000005050         ABC Supply Inc.                                   VENDOR                            VENDOR
    0000005051         BASF                                                    VENDOR                            VEDOR
    and so ON
    How can assign a Fixed value to the member Propert?  Can I achieve it in Conversion file....? 
    ( My atempts failed...).
    Any suggestion recommendation would be gretaly appreciated.
    Munna.

    Hi,
    For adding fixed values to the properties, you can use the transformation file. In the mapping section, you can specify a constant value. This value will be written to properties of all the members while importing master data. However, for parenth, its a bit different. First thing is that, you need to have a member called CUSTOMER, then only you can have CUSTOMER in the parenth column. Even if you add it and use the mapping section for this purpose, then it will write CUSTOMER to parenth for all the members (even to CUSTOMER member). And this will be wrong. So, you will need to write it manually.
    Hope you got the idea.

  • SSRS MDX Query Dimension Properties Missing

    I have been stumped on this for a few days thought I'd throw this out here. I've read every related article in the forum regarding MDX Queries and Dimension Properties in SSRS Report Developer and haven't found a case exactly like this with a solution that
    works.
    Environment is SQL 2012 SP1 Cum update 5
    I am doing a rather generic query out of MS Project Servers OLAP cube and I can't get the dimension properties to show up in the flattened output for my dataset. See below.
    SELECT
    NON EMPTY { [Measures].[FTE est] } ON COLUMNS,
    NON EMPTY {
    [Value_Stream_Project].[Value_Stream_Project].ALLMEMBERS *
    [Project Status_Project].[Project Status_Project].ALLMEMBERS *
    DESCENDANTS([Project List].[Project List Level 02].ALLMEMBERS)*
    DESCENDANTS([ProjectManager_Project].[ProjectManager_Project Level 02].ALLMEMBERS) *
    [Planner_Project].[Planner_Project].ALLMEMBERS *
    [Time].[Month].ALLMEMBERS
    DIMENSION PROPERTIES
    MEMBER_CAPTION,
    MEMBER_UNIQUE_NAME,
    PARENT_UNIQUE_NAME,
    LEVEL_NUMBER ,
    [Project List].[Project List Level 02].[Start Date],
    [Project List].[Project List Level 02].[Finish Date]
    ON ROWS
    FROM (
    SELECT ( STRTOMEMBER(@FromTime, CONSTRAINED) : STRTOMEMBER(@ToTime, CONSTRAINED) ) ON COLUMNS
    FROM (
    SELECT ( STRTOSET(@RBSResource, CONSTRAINED) ) ON COLUMNS
    FROM (
    SELECT ( STRTOSET(@ProjectStatusProject, CONSTRAINED) ) ON COLUMNS
    FROM (
    SELECT ( STRTOSET(@ValueStreamProject, CONSTRAINED) ) ON COLUMNS
    FROM [MSP_Portfolio_Analyzer]))))
    My issue is the [Project List Level 02] dimension Properties  (below) are not showing up in the Query designer output, aren't being generated as fields in the dataset and can't be referenced as a property in an expression (i.e. Fields!Project_List("Start
    Date") )
    [Project List].[Project List Level 02].[Start Date],
    [Project List].[Project List Level 02].[Finish Date]
    The odd part is if I change the above two rows in my query to this :
    [Project List].[Start Date],
    [Project List].[Finish Date]
    The Query designer shows the properties in the output but leads to  2 other issues,
    1) I have to modify the generated Dataset field values to remove the [Project list Level 02] in the Level unique name like this
    Before<?xml version="1.0" encoding="utf-8"?><Field xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xsi:type="MemberProperty" PropertyName="Project List - Start Date" LevelUniqueName="[Project List].[Project List Level 02]" />
    After
    <?xml version="1.0" encoding="utf-8"?><Field xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xsi:type="MemberProperty" PropertyName="Project List - Start Date" LevelUniqueName="[Project List]" />
    2) I have to restrict my cross join to only the current level (Level 02) or it expands the results to the parent hierarchy of the Project List dimension and skews my measure summaries.
    I've tested the query in SSMS directly and the properties are showing up just fine for those dimensions using the original syntax.
    Any help would be appreciated.

    Hi there,
    Which data source provider are you using?  Are the connection strings used in SSMS the same as SSRS? Doing a profiler trace against Analysis Services might point to differences in how the connection is made or query is parsed.
    This may help.
    http://www.sqlchick.com/entries/2011/10/23/pros-cons-of-using-the-ole-db-provider-for-ssas-100-when-rep.html
    Did you try using With clause to make a friendly name for the member properties?
    http://melick-rajee.blogspot.ca/2012/04/how-to-get-member-properties-in-mdx.html
    cheers,
    Andrew
    Andrew Sears, T4G Limited, http://www.performancepointing.com

Maybe you are looking for