‘View Details’ Button Does Not Work on EDT Fields Used in Forms Displaying Records from Customized Tables

In previous versions of Microsoft Dynamics AX, table relationships could be defined in the Application object tree under the Relations node of either an EDT node or a specific table node.

 

Starting with Microsoft Dynamics AX 2012, the use of relations on EDT is obsolete and should be deleted in its future versions.

 

All table relations defined under an EDT should be migrated since they should be defined on tables only. If this is not done correctly, the ‘View details’ option can be unavailable for EDT fields used in forms displaying records from customized tables. This problem might occur even though the ReferenceTable property on the EDT is set to some table and this EDT matches the type of the primary index from the corresponding reference table.

 

Our team came to a different possible solution to this problem, which is explained in the text below:

 

Firstly, you need to create a self-relation in the table whose primary index matches the EDT.

 

 

Another option is to create a hidden menu item button, which opens the main form of the data from the table whose primary index matches the given EDT.

 

Next, on the grid displaying the records from this table set this button as a default action. ‘View button’ option will appear on right-clicking the first field in the grid.

 

It is important to note that this is not the best solution since this works only on forms containing a grid with the corresponding table set as the main data source.

 

If you want to use this field from the same table in other forms, the ‘View details’ button won’t be shown again, unless the previously mentioned conditions are fulfilled. This approach is used in the Sales agreements list page.

 

 

How to Set Up Team Foundation Server on Visual Studio in Dynamics AX 365?

In this blog post, we will provide you with the required steps to configure your VS to enable source control on your model.

 

Create a New Model and Project

 

The first thing we need to do is to create a new project and a model which will be used for that project. You can find out here how to do that.

Connect to Team Foundation Server

 

The next step is to connect to your Team Foundation Server. To do this, we need to follow up these steps:

 

• Open the Team Explorer window (View -> Team Explorer)

 

• Click on the manage connection button and select Connect to Team Project

 

 

• From the newly open window click on Servers… button and add your TFS and connect to it

 

 

Create the Folder Structure

 

Before starting with development, we need to open the Source Control Explorer and create the following recommended folder structure in our team project.

 

 

 

The source XML files organized by packages and models will be held in the Metadata folder and our VS projects will be in the Projects folder.

 

Mapping

 

Next step is to configure the mapping for the Metadata and Projects server folder to a local metadata/project folder that will hold our VS solution and project files.

 

Add the Descriptor

 

The last step required to be done is to add the mapping for the Descriptor or you will face the problem a lot of people encounter during this configuration “The model <ModelName> specified on the project cannot be found.”

 

To do this first create such folders locally inside your model repository and drag/drop the Descriptor and XppMetadata folder from there to the TFS branch in the VS.  This will automatically create the mapping for these two folders.

 

 

You can then start with development in your newly configured environment.