Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    #16
    If you want in-depth help from Support, don't waste Support's time responding to baseless criticism of the product. This is the second time you've done so and rather than further help, the only result in going to be getting ignored.

    Support already gave you an approach:

    some kind of filtering before showing the cube as such, which again would generally be a better UI, as well as more efficient.
    To elaborate: a tree facet with 25,000 nodes showing every single customer is a terrible UI, and will result in the user navigating forever to find the data they actually want to see, all the while loading data they don't actually care about, which slows down the application for all users.

    Instead, *before showing the cube*, provide a UI that allows the user to select specific customers to display. This is more usable and more efficient.

    In sum, the cube doesn't support lazy loading of facet values by default because that's a really bad UI with poor performance.

    Comment


      #17
      Originally posted by Isomorphic View Post
      If you want in-depth help from Support, don't waste Support's time responding to baseless criticism of the product. This is the second time you've done so and rather than further help, the only result in going to be getting ignored.

      Support already gave you an approach:



      To elaborate: a tree facet with 25,000 nodes showing every single customer is a terrible UI, and will result in the user navigating forever to find the data they actually want to see, all the while loading data they don't actually care about, which slows down the application for all users.

      Instead, *before showing the cube*, provide a UI that allows the user to select specific customers to display. This is more usable and more efficient.

      In sum, the cube doesn't support lazy loading of facet values by default because that's a really bad UI with poor performance.
      Fist: I'm really upset for such reply ! we are a leading software house based in Egypt & we are evaluating the Enterprise edition specially for the cube functionality. Unfortunately what we get from you is a very non specific answers like "the cube has been shipping with a variety of complex business applications for years" or just like the post you mentioned, the FAQ was talking about copying & pasting things actually we dun need to run the cube! why there is no a single project for each important functionality for example ?! , I think the best way for getting advance is to listen to the evaluators complaints!

      Second: Of Course that wasn't what I mean to view 25 customers on the screen ! what I meant is to display the hierarchy for the customers & only view some customers related to some classification when this classification get collapsed.
      the problem here is that the cube requires this full facet values tree of customer classifications -with the customers as the facet values tree leafs - all together! that absolutely is making a performance hit, it would be okay to load the facet value child list on collapsing it. Hope things now are clearer ..

      Comment


        #18
        We now explained twice that you need to provide a UI to filter customers before the cube is displayed.

        This completely solves everything you think is a problem about the cube.

        If you don't understand an explanation like this, you need more intensive help such as training and consulting services.

        This is also indicated by the fact that you still think there's something wrong with the Optional Modules documentation, which continues to be correct.

        We offer various commercial services you can take advantage of.

        We will not make further attempts to help you on the forums, as clearly you are not going to be able to take advantage of help in this format.

        Comment


          #19
          Originally posted by Isomorphic View Post
          We now explained twice that you need to provide a UI to filter customers before the cube is displayed.

          This completely solves everything you think is a problem about the cube.

          If you don't understand an explanation like this, you need more intensive help such as training and consulting services.

          This is also indicated by the fact that you still think there's something wrong with the Optional Modules documentation, which continues to be correct.

          We offer various commercial services you can take advantage of.

          We will not make further attempts to help you on the forums, as clearly you are not going to be able to take advantage of help in this format.
          Apart from your non professional reply (think again, why we haven't such problems with hibernate forums for example !! ) ,
          I understand the solution you are offering here! That's some workaround but still the best idea to support is the facet values lazy loading , isn't it ?

          Comment


            #20
            It's not a workaround, it's the best UI with the best performance.

            Please consider your own conduct before accusing anyone else of lack of professionalism. Baseless criticism is not well-received anywhere on the internet, and in many forums, would result in being ridiculed rather than receiving further advice, as happened here.

            Comment

            Working...
            X