Replied 26 August 2020, 12:46 am EST
Regarding the text limit, can you use names queries/procedures that are saved in the DB instead of saving large queries in the report's body.
Also, can you disable the default "DataSet" and "DataSource" dialog and create your own dialog to full your requirement:
reeView node = reportExplorer.Controls.Controls as TreeView;
var tag = node.Nodes.Nodes.Tag;
MenuItem menuItem1 = new MenuItem("Add");
MenuItem menuItem2 = new MenuItem("Edit");
ContextMenu cm = new ContextMenu();
TreeNode treeNode = new TreeNode();
treeNode.Text = "Data Sources";
treeNode.ContextMenu = cm;
treeNode.Tag = tag;
Hello a procedure won't work because oracle procedures can't return sql query results like microsoft sql do. Measures like storing large portions of a report's query inside a database view to shorten a query could work but then they would need the help of other departments to work around this length limitation. We've also explored other options like using the With statement to shorten code, remove comments, shorten alias names.
We've had to do refactoring to get around this limitation. It is possible to do these things but then, besides having to deal with the inconvenience of having to do that, any time a user would need to edit the report they would have to go through a bureaucratic process to get database objects updated.
I've tried to put your code sample in the project in various places but the menu items are not showing. Is there a place I should place it? If there was an alternative window that could be loaded then that window could have the textbox for the query without the 32767 limitation and then could probably enter the query into the dataset through code. Although then the user would be missing out all the other configurations that window provides.
I've also thought about putting longer queries in the rdlx file itself except I think it would get clipped if anyone tried to modify the query from that current textbox length issue.