Bug for Drag View

YangyangCai shared this question 4 years ago
Answered

Hi Team,


Hope you are having a good day today.


I found a bug for reports which is created by drag view.

We use patch 20160727.


And the issue looks as follows:


We applied total to the columns for the following which is created by drag view, but it shows two rows.


/wNp8Hm99lsl+QAAAABJRU5ErkJggg==


We did not tick the sub total when we custom field's format.


/9Pyr8lczx64rvAAAAAElFTkSuQmCC


Could do you please advise us how to remove the grand totals from this report?


Much appreicate if you could address this issue ASAP for us.


Regards,

Nancy

Comments (3)

photo
1

Hi Nancy,


In my tests on your build, this functionality worked as expected:


e184bed3ee5c20d753f9d4661600b343


From what you have sent, it seems that there is some other option enabled to produce these, though I cannot figure out what.


If you create a fresh report on a fresh data sources does this same thing happen?


Regards,

Nathan

photo
1

Hi Nathan,

I am sorry for late reply.

I have tried to create a new report with drag view, and do not have this issue.

I think this issue is caused by the upgrade between different patches.

In order for you to investigate further for us, I have sent you through the export report and its report format.

Much appreacite if you could find out the reason and solution for us.

Feel free to let us konw if you need more details.

Regards,

Nancy

photo
1

HI Nancy,


Thank you for the elaboration. If this is specific to an upgrade path it would be most useful if you could tell me what build you came from so that I can replicate this.


Regards,

Nathan

photo
photo
1

Hi Nancy,


Any luck in resolving this one? I am going to set this ticket to closed for now, but if there is anything else I can do to help here, please just let me know and the case will be re-opened!


Regards,

Nathan

photo
1

Hi Nathan,


I am sorry for late reply.


We are currently on the build 20160727-autoit.


My colleague has figured out what has happened. And I will show you how we fixed it.

1. The following chart has this issue.

7060ab5a0f95727a530be2310276be84


2. I edit this report, and you will see that the section does not have data.

04c6f907eec1ea7aa3aa6f98be99d803


3. I put the RO Type into this section for testing.

a0dfe2eff415567581678926f2b4346a


4. Open the setup for section field, you will see that the grand total has been turn on. That is wried.

ac22ecf36f62748919802edaf24bba19


5. Then I disable the grand total, remove the field from section part

9446f96410c01ba91551beeda263b577


6. All good with current report.

ac0df288796de71fcb8ea0b08a8e4211


The following is our patch roadmap, It seems that for some reason during the upgrading between 20151209 to 20160727-autoit, this error happened due to grand total has been default to be open.

cc83741b645404430d3ec994e4090763


Much appreciate if you could replicate this issue, and advise us does this issue has been fixed for 7.3+ release.


Regards,

Nancy

photo
1

Hi Nancy,


Thank you for the thorough replication steps. I have a very busy day ahead of me, but I will attempt to replicate this as soon as I can, and get back to you!


Regards,

Nathan

photo
1

Hi Nathan,


Thanks for your patience.


This issue happened due to upgrade from 20151209 to 20160727 build, will not happen for new created report. I think using sql to update grand total to be off is easy strategy rather than keep testing. Could I ask for a query to update grand total to be off for all charts?


Regards,

Nancy

photo
1

Hi Nancy,


I will make note of the upgrade path incase other clients experience this as well. I was able to remove this by editing the reportformat table:

85458fd170f8134a081f4f76c34452f4


UPDATE reportformat SET FormatCode='false' WHERE EntityCode='DATA' and FormatTypeCode='GRANDTOTAL'
It is worth again noting that you will need to clear the cache prior to observing this take effect (restart the instance).


Let me know if this works for you!


Regards,

Nathan

photo
1

Hi Nancy,


Any luck with the query?


Regards,

Nathan

photo
photo
1

I am going to set this ticket to closed for now, but if there is anything else I can do to help here, please just let me know and the case will be re-opened!


Regards,

Nathan