Comments (31)

yes the Header Lock functionality is still available in 7.2 and the setup is in a different place in 7.2 when compared to that older version of Yellowfin you saw in that article. You will have to go to Report Formatting -> Data -> Header Lock as shown in the attached screenshot "HeaderLock.png".

I hope you can find it now, if not please send a screenshot of what you are seeing in the Report Formatting screen.

I've just tested the header and column locks in my 7.2 20161024 YF in a Firefox browser and it worked. I've attached a video that starts off showing the locks turned off, then I turn them on and they work.

I've just thought of something, the header and column locks only work in reports that are in a dashboard tab or storyboard. They don't work for standalone reports, is that what you are trying them in?

OK, I've just converted video to AVI format and emailed it to you, unfortunately they are larger files than MP4 but hopefully the 14 MB file is not too large for your mail server's policy. Please let me know if you don't get it, it most probably means that your mail server blocked it.

I used the 7.2 20161207 to do testing, but found the function does not work. My thinking is that is this function relates to web.xml file? Because we use update rather than installer when we do upgrade, and some files would not be updated.

If you do not mind, hope you could do a web session with me, because I think it would be a good way to save our time, I need report his issue next Monday.

thanks for your time for the screenshare this afternoon, and now I have found out which tables and columns we should check:

if Header & Column lock are turned OFF then there are 2 extra rows in the ReportFormat table, however, if they are turned ON then there are no extra rows in that table (because it's the default setting)

I see what you mean - I started off with the wrong 6.3 build. So I deleted that and started all over again, I've attached the full installer log and the 2 patch logs, they are all the same builds as yours. Please be aware that sometimes the publish date can be different from the build date, I found this in the 7.2 July update, please look at the below screenshot of our builds folder, there is no 20160727 so I used the official published build which is 20160728:

and after I went through this upgrade path I still couldn't reproduce the issue. So it must be caused by something else.

On Monday lets turn on DEBUG logging and see what happens when we load the tab and scroll down.

I will have to ask the dev team leader to allocate a developer to do this live debugging, and then I'll have to get the developer's approval if that 10pm time is OK for them.... Is that for security reasons that you can only open the connection at 10pm?

I think arrange a developer to come over our office maybe is a good way to save time. I am not sure the web live debugging will help us a lot. I could open the connection all the time, it depends on your time.

I'm sorry but we won't be able to get a developer to visit you, so we'll have to go with the remote connection. However, before we organise that meeting, I was wondering whether I myself could have a final look at your test environment again, the reason being that I just want to make 100% certain it's not something silly that I missed! I could send you a GoToMeeting invitation, you wouldn't even have to waste your time attending - you could just leave me to it. It's just a final check, won't take very long. What do you say?

thank you for your time again for today's screenshare session in which we went through the Auto-IT upgrade process and we found that after we had upgraded to 7.2 July build the issue did not exist. However, there is one more step which we agreed you will try tomorrow....and that step is to run the huge Auto-IT content SQL script that fills up the YF DB with all of the content.

I look forward to hearing the results of the final step you are doing tomorrow....

I am happy to tell you that I found the issue and it is related to the configuration table in our YF DB:

When I ran the following sql, the problem is fixed. The issue is because our team always import the same YF file on the backend and configure table always be the same, and I did not realize we have turn off customerdashboardscrollbars.