Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Severe Severe
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Notice:
      When an issue is open, the "Fix Version/s" field conveys a target, not necessarily a commitment. When an issue is closed, the "Fix Version/s" field conveys the version that the issue was fixed in.

      Description

      There is a number of issues with calculated members which reside not on top level of hierarchy.

      1. The following MDX causes "Member not found" error in Mondrian 2.4.2 (works in MSAS 2000)

      with member [Product].[Food].[Test] as '[Product].[Food]'
      select

      {[Measures].[Unit Sales]} on columns, {[Product].[Food].[Test]} on rows
      from Sales

      2. The following MDX returns the list of strange members. Should return empty set.

      with member [Product].[Test] as '[Product].[Food]'
      select {[Measures].[Unit Sales]}

      on columns,
      [Product].[Test].children on rows
      from Sales

        Issue Links

          Activity

          Hide
          Mondrian Importer User added a comment -
          {anikitin}

          , 09/24/2007: IP, Artifact Created: 217.119.25.147 |

          {willgorman}, 01/11/2008: artifact_group_id, 100 | {willgorman}

          , 01/11/2008: assigned_to, 100 |

          {nobody}

          , 02/13/2008: IP, Comment Added: 64.132.248.34 |

          {willgorman}, 02/15/2008: IP, Comment Added: 64.132.248.34 | {willgorman}

          , 02/15/2008: status_id, 1 |

          {willgorman}, 02/15/2008: resolution_id, 100 | {willgorman}

          , 02/15/2008: close_date, 0

          Show
          Mondrian Importer User added a comment - {anikitin} , 09/24/2007: IP, Artifact Created: 217.119.25.147 | {willgorman}, 01/11/2008: artifact_group_id, 100 | {willgorman} , 01/11/2008: assigned_to, 100 | {nobody} , 02/13/2008: IP, Comment Added: 64.132.248.34 | {willgorman}, 02/15/2008: IP, Comment Added: 64.132.248.34 | {willgorman} , 02/15/2008: status_id, 1 | {willgorman}, 02/15/2008: resolution_id, 100 | {willgorman} , 02/15/2008: close_date, 0
          Hide
          Mondrian Importer User added a comment -
          {nobody}

          , 02/13/2008: Logged In: NO

          I did some investigation on #1, Query.lookupMemberFromCache() compares defined calculated members to the string "[Product].[Food].[Test]" via their unique name string. In this case, the unique name resolves to "[Product].[All Products].[Food].[Test]" so there is no match. We'll need a more robust mechanism for resolving these names to fix the problem.

          Show
          Mondrian Importer User added a comment - {nobody} , 02/13/2008: Logged In: NO I did some investigation on #1, Query.lookupMemberFromCache() compares defined calculated members to the string " [Product] . [Food] . [Test] " via their unique name string. In this case, the unique name resolves to " [Product] . [All Products] . [Food] . [Test] " so there is no match. We'll need a more robust mechanism for resolving these names to fix the problem.
          Hide
          Mondrian Importer User added a comment -
          {willgorman}

          , 02/15/2008: Logged In: YES
          user_id=160824
          Originator: NO

          Fixed in check in #10575

          Show
          Mondrian Importer User added a comment - {willgorman} , 02/15/2008: Logged In: YES user_id=160824 Originator: NO Fixed in check in #10575

            People

            • Assignee:
              Julian Hyde
              Reporter:
              anikitin
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: