Default content level for new dimension on all logical table sources — Oracle Analytics

Oracle Analytics Cloud and Server

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Default content level for new dimension on all logical table sources

Received Response
21
Views
11
Comments
938767
938767 Rank 4 - Community Specialist

I work regularly on an OBIEE repository with 100+ facts and 200+ logical table sources.

Every time I add a new dimension, I have to go one-by-one to set the logical level for that dimension in each and every table source.  This takes nearly an hour just to add a single dimension

Is there any way, when adding a dimension, to default all LTS to a specific logical level?

https://i.stack.imgur.com/DwMUx.jpg

«1

Answers

  • choracy69
    choracy69 Rank 6 - Analytics Lead

    Hi,

    Can you try: More --> Get Levels or More --> Copy From?

    pastedImage_0.png

    I also use this functions and it's workking fine.

  • 938767
    938767 Rank 4 - Community Specialist

    I don't think that really solves the issue.

    When I create a new dimension, I want to set the content level to 'totals' for ALL existing logical table sources by default. Currently I have to go through each one by one and do that which is quite time consuming.

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    Are you a professional working with OBI and getting paid for it?

    Yes? Then that's what's normally called "doing your job".

    Thanks for playing, better luck next time

  • 938767 wrote:... is quite time consuming.

    Well, knowing the RPD is a one-shot activity and so you have to do it only once I would not say it's wasted time but it just takes the time it's supposed to take.

    As you set it by default to TOTAL it means that most of the time your "new" dimension are non conformed dimensions.

    So maybe you can also challenge your choice of single business model?

    If most of your dimensions are non conformed and works only for 1-2 fact tables over the 100 does it really make sense to keep staying with a single model approach?

    Actually this "quite time consuming" is because of this choice of single model and fitting into it lot of tables which doesn't really share a lot between them ...

  • 938767
    938767 Rank 4 - Community Specialist
    Christian Berg wrote:Are you a professional working with OBI and getting paid for it?Yes? Then that's what's normally called "doing your job".Thanks for playing, better luck next time 

    I'm asking if there is a way to do my job more efficiently.

    It is a tedious menial task and I'm simply asking if there is a way to do it faster.

    If you don't have anything to contribute, why are you commenting?

  • Ok, so keeping it short: not really.

    And for sure not setting itself as "total" (as in general it's more the other way round and a normal default value would be the most detailed level of the hierarchy.

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    a) Fun has never killed anyone

    b) The initial post implicitly states that your "100+ facts and 200+ logical table sources" are in one single business model since otherwise this would not be the case: "Every time I add a new dimension, I have to go one-by-one to set the logical level for that dimension in each and every table source." And especially "This takes nearly an hour just to add a single dimension".

    And that's basically a questionable design choice anyways.

  • 938767
    938767 Rank 4 - Community Specialist
    Gianni Ceresa wrote:938767 wrote:... is quite time consuming.Well, knowing the RPD is a one-shot activity and so you have to do it only once I would not say it's wasted time but it just takes the time it's supposed to take.As you set it by default to TOTAL it means that most of the time your "new" dimension are non conformed dimensions.So maybe you can also challenge your choice of single business model?If most of your dimensions are non conformed and works only for 1-2 fact tables over the 100 does it really make sense to keep staying with a single model approach?Actually this "quite time consuming" is because of this choice of single model and fitting into it lot of tables which doesn't really share a lot between them ...

    I agree that multiple business models would be better, but I unfortunately inherited this RPD with a single model, and changing at this point is really not feasible.

    At this point I'm considering exporting the RPD XML and just adding the content levels with a script.

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner
    938767 wrote:At this point I'm considering exporting the RPD XML and just adding the content levels with a script.

    Good god why you think I didn't put "c) You can XML hack the RPD." ?

    Because you have about 9 chances in 10 to destroy your RPD . That's definitely in the category of "Do As I Say Not As I Do".

  • 938767 wrote:At this point I'm considering exporting the RPD XML and just adding the content levels with a script.

    Honestly I would say you are safer if you still spend 1h doing it by hand.

    The XML manage content level by reference IDs, you get it wrong and you screw up your RPD.

    So if you aren't extremely comfortable (and familiar) with the MDS XML format you have more chances to create more issues than fixing thing ...

    But of course you can do it