Announcement

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

    Collapsing bug in cube when first column facet is tree

    Hi,
    I am facing one more bug in the cubegrid where when the first column facet is a tree, the collapse functionality doesn't work. The bug can be reproduced in the analytics example: http://www.smartclient.com/#analytics.
    After opening the cubegrid if you try to collapse the first column facet value, nothing happens, but if you collapse the values of the second column facet, then the collapsing functionality of the first column starts to work.
    Is there a workaround? When will this bug will be corrected?

    #2
    Just a note to say we've verified there is an issue here. We're not yet sure how involved the fix will be.

    Comment


      #3
      I'll have to put the system in production next week. Is there a temporary workaround like sending an event after creating the cube?

      Comment


        #4
        This has been fixed - fix will be present in the next nightly build (of 8.1.x or 8.x).

        Comment


          #5
          Has this fix been included in 8.2?

          Comment


            #6
            No, but 8.2.x nightlies have it (these have just fixes relative to 8.2).

            Comment


              #7
              I've made a test with 8.2p and there is a new problem. When I expand the first column, the cube keeps making requests showing the loading dialog.
              Does this has been fixed only in nightlies?

              Comment


                #8
                That's not a known bug, please provide details.

                Comment


                  #9
                  Before switching the version, when clicking in the first column, the query was:
                  http://localhost:49539/Servicos/Servidores/ServicoCuboServidoresOrgaoCargo.ashx?tipoApresentacao=consulta&ORGAO=Total&CARREIRACARGO=E.Carreira.000&CARREIRACARGO=E.Carreira.024&CARREIRACARGO=E.Carreira.018&CARREIRACARGO=E.Carreira.030&CARREIRACARGO=E.Carreira.020&CARREIRACARGO=E.Carreira.031&CARREIRACARGO=E.Carreira.016&CARREIRACARGO=E.Carreira.029&CARREIRACARGO=E.Carreira.035&CARREIRACARGO=E.Carreira.038&CARREIRACARGO=E.Carreira.014&CARREIRACARGO=E.Carreira.036&CARREIRACARGO=E.Carreira.015&CARREIRACARGO=E.Carreira.042&CARREIRACARGO=E.Carreira.039&CARREIRACARGO=E.Carreira.007&CARREIRACARGO=E.Carreira.028&CARREIRACARGO=E.Carreira.130&CARREIRACARGO=E.Carreira.021&CARREIRACARGO=E.Carreira.034&CARREIRACARGO=E.Carreira.097&CARREIRACARGO=E.Carreira.025&CARREIRACARGO=E.Carreira.013&CARREIRACARGO=E.Carreira.099&CARREIRACARGO=E.Carreira.022&TOTALSERVIDORES=TOTAL&_operationType=fetch&_dataSource=dsServidoresOrgaoCargo&isc_metaDataPrefix=_&isc_dataFormat=json
                  After switching version library, the query turned to:
                  http://localhost:49539/Servicos/Servidores/ServicoCuboServidoresOrgaoCargo.ashx?tipoApresentacao=consulta&ORGAO=E.POLICIA%20CIVIL%20DO%20DISTRITO%20FEDERAL%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20&CARREIRACARGO=Total&TOTALSERVIDORES=TOTAL&_operationType=fetch&_dataSource=dsServidoresOrgaoCargo&isc_metaDataPrefix=_&isc_dataFormat=json

                  Which queries data from the second column facet, and the data returned can't be interpreted.

                  Comment


                    #10
                    Sorry, without the facets and the data and settings, just showing us some random URLs won't help. The quickest way to make us able to reproduce the problem is to tweak one of the samples until you can reproduce it, then show us the changes required.

                    Comment

                    Working...
                    X