steveo250k

The Read-Only permission fixed worked for me. We upgraded from 6.0.0 to 6.2

Thanks! This helped me too. Just what I was looking for. I wish, on the Jasper Server, it had the option to switch between the Relative Date and Calendar views (as in Ad Hoc reports). I can enter either a date or relative date to the field and either work. But, it's not intuitive to the user that they have both options.

Using the new "Calulcated Fields", I'm trying to calculate the number days between specific dates without counting weekends. Right now, I'm using the below IF statement but I want to exclude weekends. Please help. IF(ElapsedDays("Origin Arrival Date Date", "Ready Date") >= 3, 'DELINQUENT')

I'm trying to create a calculated field in an ad hoc using multiple IF statements. The thing is I'm not sure how to connect the statements. Below are the statements that i'm trying to use. IF("Origin Appointment Time" == null, 'NO APPOINTMENT') IF(ElapsedHours("Origin Appointment Time", "Origin Arrival Date") < 2, '< 2 Hours') if(ElapsedHours("Origin Appointment Time", "Origin Arrival Date") > 2, '> 2 Hours') if(ElapsedHours("Origin Appointment Time", "Origin Arrival Date") > .5, 'ON TIME')

Yes I have. I have at least 3 open through the support page.

I do parameterize, and that's the problem. My default parameters are often wide. For example I have some reports where several parameters are optional. The default is empty which my query interprets as ALL (e.g., all locations, all vendors, etc.). When my users run the report, they will set one or more parameters. But the design is to initially leave the parameter fields blank. Switching to preview mode with the empty defaults would, in this case, cause the report to run for all locations and all vendors. This is a very large report and would take a long time. It's not realistic for the way the user would run the report. Sure, I could set other defaults, but then I would not be testing the report as I want to deploy it. I would also have to remember to remove the defaults or set them to what I need before deployment. It doesn't look like Studio honors the parameter default I have set up either. I set some default start and end dates to be last month. In preview all I get is the current date which I have to actively select. Now Studio says I have to set a date before it will run. Some parameters I want to be a specific default, Studio doesn't honor the default. Other parameters are purposely not set so they can be set at runtime and Studio takes off with that then blows up. What gives?!? I don't like the way the element properties displays in Studio either. Studio groups properties across several tabs. iReport lists the properties in one tab. In both I have to scroll. I suppose in time I'll learn which property is on what tab. But I think adding sub tabs just makes Studio more cluttered and less efficient. Sometimes the buttons on the individual property element drop off the right edge of the screen. Resizing the frame to make it wider does not fix the issue. Even though I have a repository view open in Studio, when I try to upload a new version of the report I have to click a different button and navigate to the correct folder in the repository. One place to download from the repository (or run). Another, completely different process to upload. Every time I save a report file I'm asked if I want to upload it. No I don't. I like to frequently save my work. But I don't need to upload it to the server everytime. This just wastes time. There is an option (every damn time) to not see this request anymore. Most applications with such an option assume no. Studio assumes yes I want to save and don't ask again. This is the opposite of what I want to do. iReport lets me save whereever I want. I have a source control workspace where I maintain my reports. Studio forces me to save in the Eclipse workspace. I don't want all the Eclipse project clutter in my source controlled work area. I find Studio less than efficient, cluttered, and hard to work with. I also work with Eclipse for general Java development and with similar IDE based tools.. The issues I see with Studio are not because it's Eclipse based. I stand by my claim that Studio is not ready for prime time. Why would I want to migrate away from something that works well in the hope they fix the problems with the replacement?

Where is this added? Report level? I'm using iReport.

I wish someone would answer this. I have the same question, where does this code go. I'm using iReport and/or Studio. I'd like to give the user the option when running the report. I see similar posts that give this type of Java code, and it makes sense. But I have no clue how to implement it.

What happened to the link?!?! This looks like what I need.

I'd like to know too.

I've been using iReport and really like it. With the announcement iReport will be phased out I started using JasperStudio (5.5.0). I hate it. At first I thought it was just that I was used to working with iReport. But the more I use Studio the less i like it. I've logged a few issues with the JasperSupport who've created bug tickets. First off I think the display with iReport is much cleaner. Studio just looks so cluttered. Some of the other issues I've found include: 1) Switching to preview automatically runs the report. Wait!, I haven't set up my parameters yet. Sometimes the report takes a long time to complete before I have a chance to reset my parameters, other times it just crashes. 2) Same thing if I change the data adapter. If I switch from my test to QA connection the report takes off and runs. It seems to me to be basic to have a report run only when I tell it to. 3) $P! parameters show as errors in the Edit Query view, even when there is nothing wrong with them. 4) File Save As forces me to save in the Eclipse workspace. I have my own source control repository. Save As should let you navigate to any directory you want. Is anyone else frustrated using JasperStudio?

We are seeing the same problem, but without the 4 second delay. It worked before the 5.5 upgrade.

Thanks. That does help. I was heading in this direction as I compared the Ultimate Guide on Views (chapter 2) and Reports (chapter 3). I was getting confused because they share much of the same functionality and steps. As a user it seemed like extra work. Create a view then create a report, that looks almost exactly like your view. As a software developer it makes sense now, I can see the steps. I usually use iReport or JasperStudio to create reports and upload them to the server. I often create a domain from that SQL for my users to use as a data source for their own reports. I was writing some end user documentation and got stuck trying to explain the purpose of the view. I don't usually work with views or Ad Hoc reports, so it was new to me as well. Thanks again to all. I'm impressed with the rapid response from everyone.

BTW, thanks for the quick response. We are using the professional version. The documentation uses view and report everywhere, but not interchangably. SSo I'm thinking there is something different about a view. They even say things like you can "view a view". If I'm viewing a view and it's not a report, what am I viewing? I can save a view and create a report from it. What's the difference?

That still doesn't define a view. I can have Ad Hoc Reports too. What is the difference between a view and a report?