Unable to access the Prepare screen for a view - just clocking

Andy Swartz shared this question 6 months ago
Answered

I added a calculated field to my view "Completed Sales Master View v3." Apparently, the new field created an issue with the view because I can no longer open the Prepare screen. When I attempt this, I just get the spinner. It will not time out. It's been going on for hours.

Can you fix this? My work on a view/report cannot proceed. This is a priority for me.

Thanks.

Andy

Comments (2)

photo
1

I was able to resolve this issue by removing from the model the table that included the fields that I used for my view-level calculated field. I then restored the deleted table to the model and the offending calculated field was gone and all was well.

I would still like to know how a view-level calculated field could cause this behavior. Don't views that are attempting to render in the "Prepare" mode eventually time out?

Andy

photo
1

Hi Andy,


Thanks for your question.


There have been some bugs that were resolved with View Level Calculated Filters. Are you able to let me know which version of Yellowfin you are using, by navigating to your /info.jsp page? If you just let me know the version you are using, I can reference the release notes (public release notes are found here) and confirm whether this behaviour hs been fixed in current releases.


Kind regards,

Simon

photo
1

Simon,

We are using version 9.7.0.3.

Andy

photo
1

Hi Andy,


Thanks for clarifying that.


I've attempted replicating this behaviour, with no success. Are you 'Cloning' or 'Editing' the View when you create the Calculated Field?


What kind of Data Source is the View derived from? I've been using a MySQL Data Source and I've faced no issues.


Now that you've managed to resolve the issue with the View, are you having any more difficulties with adding Calculated Fields or does the issue no longer present?


Kind regards,

Simon

photo
1

Simon,

I was editing the view when I created the calculated field. The data source is MySQL.

The issue is no longer present. Since you were unable to replicate this behavior, I don't object if you want to just close the ticket.

Regards,

Andy

photo
1

Hi Andy, thanks for the update.


I think we don't have much of a choice to close it off, however if you ever see this again, here is what I would do;


1. Get a copy of the info_threads .

2. Get a copy of the YF logs (\yellowfin\appserver\logs)

3. Any info / screenshots to help illustrate what happened


We can then investigate further and take it from there.


Really sorry you faced this issue, and hoping this was a once-off, it not we will jump straight back into it!


Thanks,

David

photo