Showing posts with label refresh. Show all posts
Showing posts with label refresh. Show all posts

Monday, March 26, 2012

Report not refreshing

The data in the report is different from the data in source table (SQL Server). How can I refresh the data? Pressing F5 is not refreshing the data.
Thanks!I've not known F5 to not refresh before! Could the report possibly be using saved data (check report options)? Could you possibly be looking in two different databases?|||Which version if crystal are you using?|||Is crystal embedded -like within an erp system, or is it pulling directly from a database table

Report not reflecting Dataset

My SSRS 2005 Dataset refreshes fine but my report, even though I refresh isn't really picking it up 100%...it's missing an account but I know that account shows in my dataset in VS. I only am using one filter and that is fine...has no affect.

Is there a specific way to refresh my report after my dataset besides the refresh button for the report itself?

If you run the report in report designer, it will cache the data to a local file on disk (e.g. report1.rdl.data). The .rdl.data file should be refreshed if you click the green refresh icon in preview. If this doesn't work, you can always close report designer/VS, delete the .rdl.data file from disk and it will recreate that file the next you run the report by reexecuting queries.

-- Robert

|||thanks a bunch.|||

Thanks for the info on the .rdl.data, but I don't have such a file.

Two (out of three) datasets (ds) on my report are not refreshing, and if you try to run them, they err. The third dataset works fine. And, another report with 3 other datasets, works fine.

I have verified all the way back to the stored procs (SP) for the name, and a syntax check. And, in query analyzer they run.

When you look at a good dataset window, you have the SP dropdown on the upper right, which if the dataset result is displayed, the drop down is not available.

Then there's a light yellow sql section that just says that the ds 'uses' the SP name.

On one of the non working ds's, the sql section is white, has my SP name in it as tho it was sql code, and the drop down says it's an SP and shows the correct name.

I also tried a brand new project with just one of the offending ds's, and it didn't refresh or run there either.

Halp.

sql

Wednesday, March 21, 2012

Report Model Deployment : The model ID of the submitted model must match that of the

Running 2005 Beta 3 Refresh. When I first deploy, it works fine. Subsequent deployments yield the following error:

Error 1 The model ID of the submitted model must match that of the
current model. C:\Source\********.smdl 0 0
Tongue Tied

When I change the name of the smdl, it works fine. (Properties of the .smdl file)

Any ideas?

For existing models Deploy actually means Update

However if Model ID is different, this cannot be considered as Update - the model may be completely different. In this case user must remove model from server before re-deploying it.

|||

Yes, thanks.

The scenario arises when you try to deploy a model in a NEW report project which has the same name as a model designed in a previous report project.

Jean-Pierre

|||

Lev Semenets - MSFT wrote:

For existing models Deploy actually means Update

However if Model ID is different, this cannot be considered as Update - the model may be completely different. In this case user must remove model from server before re-deploying it.

How can i remove a model from the server.?

Thanks !!|||

Programmatically - by calling SOAP API method DeleteItem()

|||

Hi,

no need to do SOAP.

Just go to the reporting web site, go to the models folder and delete the report.

Re-deploy and it's updated version is back in the folder.

Report Model Deployment : The model ID of the submitted model must match that of the

Running 2005 Beta 3 Refresh. When I first deploy, it works fine. Subsequent deployments yield the following error:

Error 1 The model ID of the submitted model must match that of the
current model. C:\Source\********.smdl 0 0
Tongue Tied

When I change the name of the smdl, it works fine. (Properties of the .smdl file)

Any ideas?

For existing models Deploy actually means Update

However if Model ID is different, this cannot be considered as Update - the model may be completely different. In this case user must remove model from server before re-deploying it.

|||

Yes, thanks.

The scenario arises when you try to deploy a model in a NEW report project which has the same name as a model designed in a previous report project.

Jean-Pierre

|||

Lev Semenets - MSFT wrote:

For existing models Deploy actually means Update

However if Model ID is different, this cannot be considered as Update - the model may be completely different. In this case user must remove model from server before re-deploying it.

How can i remove a model from the server.?

Thanks !!
|||

Programmatically - by calling SOAP API method DeleteItem()

|||

Hi,

no need to do SOAP.

Just go to the reporting web site, go to the models folder and delete the report.

Re-deploy and it's updated version is back in the folder.

Report Model Deployment : The model ID of the submitted model must match that of the

Running 2005 Beta 3 Refresh. When I first deploy, it works fine. Subsequent deployments yield the following error:

Error 1 The model ID of the submitted model must match that of the
current model. C:\Source\********.smdl 0 0
Tongue Tied

When I change the name of the smdl, it works fine. (Properties of the .smdl file)

Any ideas?

For existing models Deploy actually means Update

However if Model ID is different, this cannot be considered as Update - the model may be completely different. In this case user must remove model from server before re-deploying it.

|||

Yes, thanks.

The scenario arises when you try to deploy a model in a NEW report project which has the same name as a model designed in a previous report project.

Jean-Pierre

|||

Lev Semenets - MSFT wrote:

For existing models Deploy actually means Update

However if Model ID is different, this cannot be considered as Update - the model may be completely different. In this case user must remove model from server before re-deploying it.

How can i remove a model from the server.?

Thanks !!|||

Programmatically - by calling SOAP API method DeleteItem()

|||

Hi,

no need to do SOAP.

Just go to the reporting web site, go to the models folder and delete the report.

Re-deploy and it's updated version is back in the folder.

Report Model Deployment : The model ID of the submitted model must match that of the

Running 2005 Beta 3 Refresh. When I first deploy, it works fine. Subsequent deployments yield the following error:

Error 1 The model ID of the submitted model must match that of the
current model. C:\Source\********.smdl 0 0
Tongue Tied

When I change the name of the smdl, it works fine. (Properties of the .smdl file)

Any ideas?

For existing models Deploy actually means Update

However if Model ID is different, this cannot be considered as Update - the model may be completely different. In this case user must remove model from server before re-deploying it.

|||

Yes, thanks.

The scenario arises when you try to deploy a model in a NEW report project which has the same name as a model designed in a previous report project.

Jean-Pierre

|||

Lev Semenets - MSFT wrote:

For existing models Deploy actually means Update

However if Model ID is different, this cannot be considered as Update - the model may be completely different. In this case user must remove model from server before re-deploying it.

How can i remove a model from the server.?

Thanks !!|||

Programmatically - by calling SOAP API method DeleteItem()

|||

Hi,

no need to do SOAP.

Just go to the reporting web site, go to the models folder and delete the report.

Re-deploy and it's updated version is back in the folder.