When I select a report area SQL from * some contacts, then all is fine unless some columns are in some - then it breaks with "ORAxxx no data found" error, it is easy to make it easy, because it is enough to re-apply the changes in this area, even without making any changes. However, this is not for a strong application.
Is there a combination of certain criteria that will allow SELECT * which does not break with the new column?
I know that I can create a column list from the data dictionary and then I can include it in the selection statement to select everything, but it seems that it does not have any default formatting or new columns Will be enough to go on. Instead, unbearable.
Currently using your field source (I think) "query-specific column names and valid Query "This means that a report column is clearly defined for each column in the query, and the SQL is expected to be stable.
If you have the field source to use "normal column names"), then it will still work after adding a new column, with the column heading in the name of the column title.
There is another asset there is "Maximum Number of Generic Report Columns" which is the default for 60 and is set to a sufficient value to accommodate any future column added in the table.
Comments
Post a Comment