Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Intelligence (Analytics)
Refresh datasets
mh10
Hi,
after adding some new columns in returned recordset from the Stored procedure, i am not seeing them in the preview result of dataset created already.
How to refresh the datasets/datasource so that whatever change done at backend will take effect immediately at BIRT frontend
Thanks
Find more posts tagged with
Comments
mwilliams
Hi mh10,
So, after you change your stored procedure, it isn't represented in your data set editor? Did it refresh after restarting the designer?
mh10
No...I restarted designer but still the dataset is not showing newly added columns in recordset..<br />
<br />
However, when i create new dataset it shows those newly added all columns from the recordset returned by stored procedure.<br />
........why not with already created dataset?<br />
<br />
<br />
Thanks<br />
<br />
<br />
<br />
<blockquote class='ipsBlockquote' data-author="mwilliams"><p>Hi mh10,<br />
<br />
So, after you change your stored procedure, it isn't represented in your data set editor? Did it refresh after restarting the designer?</p></blockquote>
mwilliams
mh10,<br />
<br />
When you open up an already created dataSet, try clicking on the query tab, then the output columns tab, and then the preview results tab. Not sure that that will do anything different, but clicking on the query tab and output columns tab may cause the query to be rerun prior to previewing. It's worth a shot. Otherwise, it sounds like it could be a bug to me. You can log the bug at <a class='bbc_url' href='
http://www.eclipse.org/birt/phoenix/reportabug.php'>BIRT
: Reporting Bugs and Requesting Enhancements</a>. Be sure to include a good description and screenshots.
mh10
Hi Michael,<br />
I tried what you said...but no luck......<br />
<br />
Actually i was using BIRT v2.3.1......then i downloaded v2.3.2...and imported report in it....and tried to preview dataset...but still it is not showing new changes......<br />
<br />
if it is then i think....now i have to recreate datasets again and assign related columns to x & Y axis...which will be not a good practice....i think <br />
<br />
<br />
<br />
Thanks<br />
<br />
<br />
<br />
<br />
<blockquote class='ipsBlockquote' data-author="mwilliams"><p>mh10,<br />
<br />
When you open up an already created dataSet, try clicking on the query tab, then the output columns tab, and then the preview results tab. Not sure that that will do anything different, but clicking on the query tab and output columns tab may cause the query to be rerun prior to previewing. It's worth a shot. Otherwise, it sounds like it could be a bug to me. You can log the bug at <a class='bbc_url' href='
http://www.eclipse.org/birt/phoenix/reportabug.php'>BIRT
: Reporting Bugs and Requesting Enhancements</a>. Be sure to include a good description and screenshots.</p></blockquote>
mwilliams
mh10,
Please search the bugs at the link I provided in my last post. If you don't find anything on this, please log a bug for it. If you could post the bug info in here for future reference, that'd be great. Thanks.
donino
<p>Hi, </p><p> </p><p>I confirm this bug still exists in 4.3.2. Though for reference here is a workaround to refresh a dataset based on a stored procedure without recreating it:</p><p> </p><p>1- In the query tab, change the name of the store procedure invoked, replace it with a dummy name</p><p>2- Click the output columns tab, an error message is displayed and all columns are removed</p><p>3- In the query tab, set the real name of the procedure: all columns are restored including computed columns, and this time new colummns are correctly added!</p><p> </p><p>In my case only aliases of output columns had been lost, but this is not very painful to fill this again, comparatively to recreate datasets from scratch
</p><p> </p><p>All dataset parameters are kept intact, but in the step 1 pay a special attention to the fact we should <strong>not</strong><em><strong> </strong></em>remove parameters invoked in the query, we just have to change the name of the stored procedure. </p><p> </p><p>I hope this will help someone else!</p>