Using CS20.2, unable to create a LiveReport that creates a table or modifies a table's contents

Hello All

I am struggling to create a new table for a project of ours using a LiveReport. I understand from the documentation the Allow modification flag no longer exists for new LiveReports but it is not clear what I must do instead.

Has this feature been removed from CS? If so, how else (outside of creating a module) can I create, drop, or modify tables and other SQL objects (e.g. Views), or even updating existing data.

We are using MS SQL.

Thanks,

Phil

Find more posts tagged with

Comments

Appu Nair

If OT does not allow you DB modification via LR(I highly suspect if it has been discontinued at best it might be something like if you turn on you cant change it back) but another way to create your own schema would be to stand a Form Template,Form & Table

Phil_Forshaw

Hi thanks Appu. I am using forms where they suit but hoped to have my own schema for requirements that do not really fit the form idea. I will raise a ticket.

Cheers, Phil

GregPetti

Phil_Forshaw said:

Hello All

I am struggling to create a new table for a project of ours using a LiveReport. I understand from the documentation the Allow modification flag no longer exists for new LiveReports but it is not clear what I must do instead.

Has this feature been removed from CS? If so, how else (outside of creating a module) can I create, drop, or modify tables and other SQL objects (e.g. Views), or even updating existing data.

We are using MS SQL.

Thanks,

Phil

Hi Phil!

I wasn't sure if the dev team was going to step in here but basically you have to create a database connection object (admin pages). These external objects have always existed though it used to be a WebForms feature designed for lookups. My understanding is that this way you can create different db users with different privileges to control whether the LiveReport is allowed to write.
In my opinion, if you can avoid using LiveReports it can be better, i.e. use WebForms? There are a couple of sub-tags that support this too.

Cheers
Greg

John Simon

I see this as an issue if OT has not changed their method for determining when the report is trying to perform a modification. For example this query - select createdate as "create date" from dtree triggers the error (in 16.2) when it is clearly not an update query. Can someone verify if this query would be allowed or not as a LR in CS20.2?
Cheers...

GregPetti

John Simon said:

I see this as an issue if OT has not changed their method for determining when the report is trying to perform a modification. For example this query - select createdate as "create date" from dtree triggers the error (in 16.2) when it is clearly not an update query. Can someone verify if this query would be allowed or not as a LR in CS20.2?
Cheers...

I can confirm that this works in CS20.2 (with the normal "global LiveReports database connection").

GregPetti

Greg Petti said:

John Simon said:

I see this as an issue if OT has not changed their method for determining when the report is trying to perform a modification. For example this query - select createdate as "create date" from dtree triggers the error (in 16.2) when it is clearly not an update query. Can someone verify if this query would be allowed or not as a LR in CS20.2?
Cheers...

I can confirm that this works in CS20.2 (with the normal "global LiveReports database connection").

Further to my response, it appears that as long as you have the term quoted you are ok. For example: select createdate as "create" from Dtree works but: select createdate as create from Dtree does not.

John Simon

Thank you Greg.
Cheers...