Category
Report Builder
Product Version
7.3
Use report as View
Resolved
I'm trying to create a report to use as a view. After creating report and then trying to create a report using that report as a view I get an error stated below. I'm not sure if there are stipulations on what report items can be used as a view. This is my first attempt and I don't see any documentation on it. So if someone could point me to the documentation or help out it would be appreciated. Oh no! An error has occurred during processing, please try again later
The same problem 
Hi Chad,
Thanks for getting in touch. This article is the best documentation we have for this functionality:
http://community.yellowfin.bi/topic/can-i-save-my-report-as-a-view
One note::
Cross-tab reports cannot be saved as view, the trick to work around this is to place whatever was in your "rows" into sections instead.
If you have clicked the "use as view" button, then there is really not much more that needs to be done, and the error you are seeing is most likely a separate issue.
What exactly causes this error? Are you able to use any of the columns in your report, or does this error arise when selecting what view to create the report from?
Regards,
NAthan
Hi Chad,
Thanks for getting in touch. This article is the best documentation we have for this functionality:
http://community.yellowfin.bi/topic/can-i-save-my-report-as-a-view
One note::
Cross-tab reports cannot be saved as view, the trick to work around this is to place whatever was in your "rows" into sections instead.
If you have clicked the "use as view" button, then there is really not much more that needs to be done, and the error you are seeing is most likely a separate issue.
What exactly causes this error? Are you able to use any of the columns in your report, or does this error arise when selecting what view to create the report from?
Regards,
NAthan
Hi Chad,
I was finally able to confirm that this bug is specific to SQL Server's timestamp data type, in combination with any date hierarchy function that returns a date such as "week start date" and "quarter end date". I have raised this as a defect, and will keep you updated on the status of the ticket.
I will look into the other issue we discussed later today, but may not have anything substantial for you until tomorrow.
Nathan
Hi Chad,
I was finally able to confirm that this bug is specific to SQL Server's timestamp data type, in combination with any date hierarchy function that returns a date such as "week start date" and "quarter end date". I have raised this as a defect, and will keep you updated on the status of the ticket.
I will look into the other issue we discussed later today, but may not have anything substantial for you until tomorrow.
Nathan
Hi Chad,
Just wanted to let you know that this issue appears to have been fixed (is currently in testing) and should be included March end of month build (release after the one coming on Friday).
Regards,
Nathan
Hi Chad,
Just wanted to let you know that this issue appears to have been fixed (is currently in testing) and should be included March end of month build (release after the one coming on Friday).
Regards,
Nathan
Replies have been locked on this page!