Hi, I created a report in JS studio and published is the same to Development server. It ran without any error. But when I published the same report to Production environmentm I'm getting error:
Error filling report
Can you please suggest what could the possible error that is causing it? The same report as in DEV was published and this is causing error. Unsure why is this issue occuring!
Any insights on this issue would be really healpful. Thanks!
You seemed to copy report from Development to Production by using JS studio.
If your Jasper is appropriate version, you can use Export/Import ability for JS contents.
It is easy way to copy content to another environment.
Export, Import, or Migrate Advanced Reporting Content - CA PPM - 15.2 - CA Technologies Documentation
HI Shoichi_Sugawara, I'm trying to publish my report to production environment. This is the same report that I published in development environment. The report ran without any issue in Development environment, but not in Production environment. Also, I'm with JS studio 6.2.1 for CA PPM ondemand 15.2.
If you created report by using the custom domain, please check that it exists in production.
I didn't create any domain.
Hi Monica_Rampradeep_Raj ,
Can you confirm that is there any sub-report in the main report? And
The full error message you see there.
Yeah, i'm calling sub report from the main report. And I didn't get any specific error. The screen shot in the post itself is the complete error message.
Most likely you a missing a colunm, image, subreport or input control. Does the report rely on a custom attribute that exists in the test DWH but not in Prod DWH? Is this OnDemand or OnPremise?
Yeah Steve, we use custom attribute in the report. It exists in both QA and Prod environment. Yes, it's on demand. I checked for all things, and it maps everything appropriately. I get the parameter window when I run the report, but the error is thrown when I click okay button.
Schedule the report and include stack trace to get emails and you will know the exact error
This is caused due to an attribute missed to migrate over. This is now corrected and is working as expected.