LiveReport Parameter bug?

Hi Guy's,

I have found an issue in Livereports 10.5 and 16.2 using the Word "Backup" as a parameter input

Attached is 3 images, 1 of the LiveReport with Parameters set, the next is inputting Parameters when executing the Livereport and the thrid is the result

I have replicated this at 3 sites across 10.5 and 16.2
One of these sites recently upgraded from 10 to 16.2 and this does not occur on the 10.0 system.

I have tried all maner of escape characters but it seems if the word "Backup" is contained in the parameter input LiveReports says NO
The livereport doesnt have "Use Transaction Mode" or "Use Cursor Mode" ticked either.

Anyone know how to overcome this?

Cheers
Warren

LiveReport.jpg

UsingLiveReport.jpg

Result.jpg

Find more posts tagged with

Comments

John Simon

In 16.2 we have seen if your SQL contains the word create (like "select col as create from ...") that you have to check the "Allow Database Modification" to get the report running. I suspect if you check the box your report will run. We haven't dug into the code (yet) but it feels like they do a scan for certain keywords and if those keywords are present then you have to check the box (whether your report is actually doing an update or not).

Cheers...

Nizar Ghazal

The way to get around the "LiveReport does not allow database modification" message, is to change up the wording, slightly, or as John said, check that box in the report.

In the OScript layer, there is a list of blacklisted SQL terminology that LiveReport checks against before running the report, it includes terms like create, backup, alter, and so on. If you have a Content Server SDK license, with the CSIDE plugin, you'll be able to take a peek at this.

Essentially, think any SQL system term that one's DBA may want to protect.

The thing, though, is, I believe it scans the entire contents of the transaction request, as aliases, or the like, are also picked up on.

I ran into this when I used the term "Backup" as an alias for a report, and it said I needed to enable modification. In lieu of that, I called it Bkup, instead.

NotYourAverageBear

Thanks Nazir and John, i had already tried using other SQL keywords (Create, Insert, Drop etc) but only the word Backup is affecting our environment.

Checking the Allow Database Modification as John suggested does allow it to run.

In our scenario we use a Workflow to Create a Project then copy template folders into the Project and then rename the project prepending an ADN number to the name of the project.but this issue was breaking it if the Title of the Project had the word backup in it.

Thanks for your help

Cheers

Warren