Our support engineers have assembled the top recommended solutions for you.
Microsoft Dynamics AX 2012CRM Connector in Microsoft Dynamics AX 2012Financials Management in Microsoft Dynamics AX 2012Upgrading to Microsoft Dynamics AX 2012
Microsoft Dynamics AX 2009
Application Object Server (AOS)
Enterprise Portal and Role Centers
Inventory Costing in Microsoft Dynamics AX 2009
SSRS and SSAS Integration
I am trying to export and import an AX2012 SSRS report from one environment to another (DEV to TEST) using XPO, however changes are not reflected in my destination environment. Any idea?
I have tried below things.
Cleared application cache.
Deleted SSRS report in Report manager, generated Full CIL, redeployed report
Still no luck, report changes have not come across.
Appreciate any clues.
Did you get a solution for the same, what is the best practice to move and deploy the reports between environments.
1. Try to open report in Visual Studio. If you don't see your changes in the report-> go back to dev and reopen ssrs report in Visual Studio->Save to AOD again. I had these problem in Ax2009.
2. If you don't see properly content in runned report->Check your bussines connector.
I bug I noticed in AX 2012 is that in the VS Report Designer, if you only "Save" your report it sometimes does not save to the AOT. I had to "Build" the report solution for the changes to push to the AOT, then export as XPO.
Best practice is do this following steps before you take the report xpo.
Upon making the changes to report do a save to aot in VS.
Now delete the report in report manager. now deploy the report from AOT.Check the changes in the report.
Close all Ax windows re-Open the Ax .
Now on the AOT node for the report right click and save .
If you have Verion control compare the object with earlier version to check any changes exists or not.
The above part of solution is to check whether the changes made it too XPO or not
To move the Xpo to another environment
-->Delete the report from Report manager.
-->Execute the report now, to get the report not found error
--> Remove these table records
Compare the XPO changes and just import the changes.
The object needs to be saved now in AOT.
Deploy the report now
Compile forward the DP class if any used . Complile forward the UIBuilder and controller classes.
Execute the report
PS :Most of the report's changes not reflecting occur becuase the first environment you make changes to the design the RDLC file for the report doesnt get saved back on the AOT or in your version control location
IF anything else i can help you with,
please reach me at
That's right, some times i have seen the changes are not reflected in XPO when exported.
Make sure you clear the cache in source system (Dev workspace / Tools / Caches / Refresh elements) before exporting.
I needed to restart AX session sometimes before generating XPO.
what i understand from the conversation here is that in the end, a ssrs repor xpo will be enough to be exported from the dev environment and imported correctly in the test / destination environment. Provided the changes made in the dev environment are reflected there
I am concerned about the visual studio model project that i created in the AX. It can have several files like rdlc and .moxl What if a 'save as' that solution I mean is not that solution the real source of all the report layout and logic ?
without concerning that whole VS model project, just an xpo will bring all changes in the destiny environment ? Or will we have to take care about several other files to be syncd or copied to the resulting destiny environment too form the source environment ? I hope I have not made it too complex :D
XPO will bring over all necessary files, no need to worry about the files that are generated by VS.
You just have to deploy the report after import in destination system.
Not necessarily does this do the trick.
The catch over here is do you have any datamethods in your report??
then you need these files even
some times the references will be lost during the import, might just need to open the vs project and update the reference's for business logic file etc
wheres the VSReportObject ? You mean the VS project ? The VS Project creates a dll, you mean that dll should be there in the references ?
Sorry guys but I am again confused here. How many files and different AOT nodes are to be taken care of if moving a ssrs report from 1 environment to another ? Please tell for quesry based as well as tmp table based (rdp) reports
and its maqK Venk ;)
Sorry Maqk the font got me on the wrong foot over there
AOT\Visual Studio Projects\C Sharp Projects
here the business logic files are saved. If you write any datamethod in a report
it opens a partail class with reportname.BusinessLogic kind of naming convention and is aved back to aot in the above mentioned path
normally you need
1)XPO of SSRS report (sufficient if you dont have data methods)
below things needed only if you have data methods in your report
2)AOT\Visual Studio Projects\C Sharp Projects\
or else you will have #error displaying in the text controls that use these datamethods
Normally, I tend to go to the source if the report has "old look" after deploying it. By this, I mean head over to the report manager, find the report and download a copy of the rdl. If you open the rdl in notepad, you will see it is just XML-content, and you will find any UI changes you've done in there. In addition, report manager will show the timestamp for latest deployment. It should correlate to when you last deployed the report.
As for dependencies to assemblies (code behind), they often need the SSRS to restart to pick up the changes. If you use the Powershell script to Publish-AXReport, then it will automatically try to restart the service as part of the deployment. Deploying from the AOT does not do this automatically, as far as I know.
Don't use data methods in the report. IT is supported for backwards compatibility, to the best of my knowledge. Think of the RDL and the view of the report as "just view" - location and formatting of content. Have ALL your business logic in your data provider, or as much as possible. This is the MVC pattern that will make your life easier over time. For example, if you need to convert something in the report based on some logic, try to design it in the data provider logic, and not in the report design view (ie. as a data method).
Debugging expressions hidden in the report design is tedious and time consuming. Same is data methods.
Tommy Skaue | Dynamics AX Developer from Norway | http://yetanotherdynamicsaxblog.blogspot.no/ | www.axdata.no
data methods for custom drill through feature's what i meant by this
Few of them you get through edt properties but few of them need custom drill through action in the text box jump action
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13