Issue in getting the latest version of an SSRS Report on Visual Studio

(0) Share

Report

Posted on by Hichem.Chekebkeb

3,371

Hello,

I opened an SSRS Report for edit but I am getting an old version of the report while the latest version is running on AX client.

I tried to refresh SSRS Reports node, restored the report, and did run Tools>Caches>Refresh elements but no luck.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Sohaib Cheema 49,438 User Group Leader on at

Like (0)

Report

Cannot guarantee but It may be getting a version which is saved on your local drive. Can you delete file from Local drive?

\Users\YourUserName\AppData\Local\Temp\Microsoft Dynamics AX\Dynamics AX Model Projects\ReportProjectName.

Usually as you click EDIT inside AOT, it will take you to visual studio. Make sure, do not trust on any of open TABS. Instead, open Solution Explorer and right click your report, Right click your report inside Solution Explorer and hit EDIT. Trust and start changes on newly loaded objects which are opened from solution explorer just now.

Was this reply helpful? Yes No
Suggested answer

Brandon Wiese 17,788 on at

Like (0)

Report

Do you have multiple environments on your development server? It's a well known problem that when you right click on an element in the AOT and select Edit to launch Visual Studio, that Visual Studio itself randomly ignores provided command line and just uses the default configuration on the local machine to interact with the AOT. You could be loading a report from another instance, say your TEST environment, even though you're clicking Edit from a DEV environment. I've even seen people accidentally make changes to SSRS reports in PROD after clicking Edit in a DEV instance.

One of the ways I combat this problem is to create an empty Job in the AOT of each environment named ThisIsTest and ThisIsDev, and then from the Application Explorer in Visual Studio I can easily inspect the Jobs node and be 100% certain which environment I'm interacting with, before I do anything of consequence.

There is a way to bind Visual Studio to a specific environment regardless of the local client configuration and any command line sent, I believe by placing a properly named .axc file in a specific directory. I haven't done it in a while, but I'm sure I can find a link to official instructions if you would find it useful.

Was this reply helpful? Yes No
Brandon Wiese 17,788 on at

Like (0)

Report
Various options are explained at the following link.

How to: Open Visual Studio with a Specific Configuration [AX 2012]

https://msdn.microsoft.com/en-us/library/gg889291.aspx

It explains how to use an .axc file to peg Visual Studio to a single instance.

To Create a Specific Configuration for Reports

To create a configuration for Reporting Services, run the Microsoft Dynamics AX configuration utility as an administrator, and then click Manage> Save configuration as file, and give the configuration a name like Microsoft.Dynamics.AX.ReportConfiguration.axc. The file must be saved in the PrivateAssemblies folder in the Visual Studio IDE installation directory, like the following:

C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies.

Was this reply helpful? Yes No
Hichem.Chekebkeb 3,371 on at

Like (0)

Report

Thanks for the reply Brandon,

Yes we have TEST and DEV in the same environment,

I did suspect this, so I shut down the TEST AOS to be sure that i am pointing to DEV. Additionally, I used axc file to start Visual studio as per the link you provided (Thanks for the useful link). still no luck.

Are there any additional steps to troubleshoot? This report is driving me crazy.

Was this reply helpful? Yes No
Suggested answer

Iulian Cordobin 8,201 on at

Like (0)

Report

With the TEST AOS stopped, first stop the SSRS service and the DEV AOS service. Then clean the auc and kti files you have in your user profile. Restart the services.

Second, open Dynamics AX Configuration Utility and check to see if the current configuration is the one pointing to DEV (if it's not, change it and Apply). Then open Visual Studio and try to edit again the report (in a new project).

Was this reply helpful? Yes No