Header Lock not working on CrossTab Reports used in dashboard until canvas is added to report

Zack Wilson shared this problem 2 months ago
Defect Logged

Header Lock not working on CrossTab Reports used in dashboard until canvas is added to report...

Comments (7)

photo
1

Hi Zack,

Thanks for reaching out to support.

Could you provide some screenshots for additional context here?

Thanks,

Eric

photo
1

Hi Zack,

I had a look at our developer platform and found this -

Crosstab Enabling Lock Header isn't locking header horizontally

Replication Steps
1. Create a crosstab
2. Enable Report Header Lock
3. Publish your report
4. Minimize your browser (So that you will get a scroll bar)
5. Use the horizontal scroll bar to scroll left & right
NOTE: You will notice that the header will disappear


Is this the same behavior in your case as well? I may be able to add you to this task if so.


Thanks

Eric

photo
1

Hi Zack,

Just wanted to check in to see if you had a chance to review my reply in this case.

Thanks,

Eric

photo
1

Hi Zack,


I'm going to go ahead and mark this ticket as Completed due to inactivity at this time. Feel welcome to reach out in the future.

Thanks,

Eric

photo
1

Eric,

I apologize. I never saw this in me email...

No. This is not the same issue. Though, they could be related.

DEFECT:

My issue is that the header lock works fine on the CrossTab report. However, when you go to add that report to a dashboard. The header lock does not work on the dashboard.


Inconvenient fix:

But, when you add a simple canvas, by creating 2 charts and one containing something (also an inconvenient fix), the header lock on the report magically works.


Thanks,

Zack

photo
1

Hi Zack,


Thanks for confirming for me. I've gone ahead and created a developer task to look into this behavior. I've added your organization as an affected client, and attached this ticket to the task for tracking purposes. Updates to this task will be provided here as they are available. I'll in turn mark this ticket as Defect Logged for now; feel welcome to reply here with any related inquiries.

Thanks,

Eric

photo
1

Hi Zack,

sorry to double post, a little quick on the draw!

Thanks for the clarification, this was not hard to replicate -


3d84c8a7173623760c2dbeaab75f7eda

I've gone ahead and created a developer task to look into this behavior. I've added your organization as an affected client, and attached this ticket to the task for tracking purposes. Updates to this task will be provided here as they are available. I'll in turn mark this ticket as Defect Logged for now; feel welcome to reply here with any related inquiries.

Thanks,

Eric