X-Read report in ax 2012 R3 customization - visual-studio-2013

I want to customize the X-Read Report in MD AX 2012 R3 which is generated on close shift operation.
The problem is that I do not know Which project or .cs file to be used for its customization in services solution.
Please Help!

Related

Application explorer shows "Default (cus) [CUS Model]"

Background: I'm trying to edit an AX Report in Visual Studio. I have previously been able to create reports in VS and integrate them into AX. But I haven't used this in several weeks. Now, suddenly it doesn't work anymore.
Symptoms: When I open Visual Studio the Application Explorer does not show our actual AOS but instead says "Default (cus) [CUS Model]". update: As it turns out the Application Explorer does connect to the right AOS. It just displays this default name (and now since resetting VS user data is fixated on the USR-layer)
Attempted solutions:
Setting /AxConfig parameter in Visual Studio shortcut. I have the exact same shortcut as my coworker who does not have this problem
Editing the Ax Config via AxCliCfg.exe
Importing, Applying, Refreshing and Re-Applying the .AXC file used to connect the AX client
Editing the registry keys for AxCliCfg both in LOCAL_MACHINE and CURRENT_USER
A ton or restarting
Checking permissions and roles in Ax, AOS Server, DB Server
I can't find anything else besides reinstalling everything. I've seen one reference to a KB2827469 that supposedly changes the way Visual Studio loads the AX configuration but can't find anything about that KB on microsoft's websites.

How to connect Visual Studio to a specific dynamics ax environment

I would like to connect my Visual Studio against different dynamics ax environments.
In particular the following two:
Development Environment
Production Environment
The purpose is to develope SSRS reports. In the production environments there are some reports which are not available in development and it would be complicated to create them. Not meaning that I'm going to develop against production (who would do such a thing?! ;-) ).
I found a tutorial which shows how to connect to a specific AOS by pointing visual studios start up parameter to an AXC file:
Tutorial for VS connection to specific AOS
When I follow the steps from the tutorial and open AX it seems that VS has connected to the correct AOS instance. See the following screenshot, showing two AOS instances one connected to Development the other to Production:
Also when I open the report from Production and from Development I can see that they are different in design, because there have been made some changed in Development.
Problem is: When I try to open a report with sample data, it always fetches the data from my Development environment. I also noticed that the SSRS report parameter #AX_UserCompany is always the company from my AX user settings in Development.
I know that VS is using my active directory user to authenticate against the AOS, but why is it always using the Development settings, even when VS is started with the Production AXC file as startup?
My question is: How is it possible, that VS pulls the SSRS report design from Production but the data from Development and what has to be done to retrieve both (Design and Data) from Production?
Any input is appreciated.
I could finally solve the mystery.
It seems that Visual Studio is always using the connection properties stored in registry. Although the report design is loaded from AX instance specified in the AXC file, the data is pulled from the AX instance specified in the registry.
The solution is to
open the Dynamics AX Configuration Utility
import the AXC file
apply the AXC File
refresh the configuration
apply again
Before you start, close AX and VS (just to be on the save side).
1. open the Dynamics AX Configuration Utility
Located in "C:\Program Files\Microsoft Dynamics AX\60\BusinessConnector\Bin\AxCliCfg.exe".
2. import the AXC file
Browse to your AXC file and import it.
3. apply the AXC File
4. refresh the configuration
5. apply again
Switch to the connection tab.
Then click apply.
Then click refresh the configuration. The WCF configuration will be regenerated.
Then click apply again.
Of course this means that you can not have two VS instances open at the same time (e.g. one connected to production and one to development). You are limited to one configuration, because of the connection properties set in the registry.
You still need two VS shortcuts:
One VS shortcut with the AXC file to development
One VS shortcut with the AXC file to production
If you want to switch between environment you need to follow step 1. to 5.
Can you close the application explorer before closing VS? Then reopen VS with your shortcut and the application explorer.
I had the issue modifying the client and BC confits not changing the target for VS.

Visual Studio 2013 CLR SP debugging on local MS SQL Server 2014

I'm currently pulling my hair out here. I have an SQL Server Database project in Visual Studio 2013, which contains a CLR SP. I have a test script created in order to call the SP and enable me to debug it. I can build, make changes and publish\deploy to my SQL Server 2014 no problem. However, when I set a break point on my test script I can step into the test, but when it then calls the CLR SP it doesn't hit any of the breakpoints I've set in it. Instead I get Dynamic Transact-SQL windows popping up with any SQL executed within my CLR SP, which is not help at all as the logic I want to debug is the c# code.
Any ideas?
Cheers,
Stu.
Please see my comment above for the answer to this problem.

Error selecting DataSet for AXDataSource in Visual Studio for Enterprise Portal development (AX 2012)

I'm working on EP development for AX 2012 R2.
When I try to add a DataSet that contains custom fields on standard tables or custom tables for a AXDataSource (in my EP user control) I receive this errors:
'DataSource "CustTable" in DataSet "DataSet1" has an unknown field "Field1"'
'Table with an id of "Table1" does not exist'
I tried to delete all the .auc files but I receive still the same problem.
At the moment I'm working with visual studio and the AOS installed on different machines.
Thanks,
Luca Ganz
You can resolve this issue by compiling the entire project which contains the objects in AX and then close AX,delete cache and then restart AOS and also close Visual Studio before restarting AOS.
Then I am 100% sure this error will not come .

Microsoft Report Viewer not Displaying R2 features properly

We have SQL Server 2008 R2 and Visual Studio 2008.
I have used the Report Viewer for displaying the reports in web application but all the R2 features are not rendererd properly in (Specially the trend images used).
I have tried to find the root cause:
1. The export functionalty is diplaying images but its not visible in webbrowser.
2. I tried to use the iFrames but simillar results i got.
Q: How i can fix the html content which is rendered but not displayed.
To solve the above problem i had to install the newer version of Microsoft.ReportViewer.WebForms (v10.0.0.0).
This is a patch provided by microsoft in visual studio 2010 SP1.
Please find the link below:
http://blogs.msdn.com/b/brianhartman/archive/2011/03/31/visual-studio-2010-sp1.aspx
Amazingly it solved all of my problems :)

Resources