111

Evaluation of cross-references is very important with such a large code base (for understanding the current solution, for impact analysis and so on). Unfortunately the experience is worse than in previous versions of AX; here are some suggestions:



  1. Allow filtering and sorting.

  2. Add filtering options similar to those in Application Explorer (by type, model etc.).

  3. When I get a list of references, I often want to look at where some references are used. Please make it possible directly from the same window. For example, I could click on a reference and use "Find reference on it". Or I could be able to expand the node and see a hierarchy of references.

  4. Re-introduce "Reference" field, such as the information where a field is written into. I know it was dropped consciously, but it was really useful. If the standard "Find Symbol Results" doesn't support things like this, it's probably time to move from it.


By the way, when you later decide to switch to SQL Server 2017, wouldn't DynamicsXRefDB form a nice graph database?

Category: Development
STATUS DETAILS
Under Review
Ideas Administrator

There are multiple suggestions here. Thank you. Some are already possible (like filtering and sorting). I will keep this idea under review and monitor the comments. We need to improve this part of the Dev Tools.

Comments

M

Could we also have the ability to select multiple results from the find references so that they can all be copied out in one go please?

Category: Development

M

Cross references in the current state are really painful.


When I try to find the code pieces where SalesLine.SalesQty is written I get 1000 matches. A lot of the results are reads or unit test classes and I don't have the option to filter out unit test classes or read/write.


I would highly appreciate a good cross reference tool with filter options.

Category: Development

M

Strongly agree on this one! cross references in AX 2012 were quite helpful as compared with D365 F&O, faced issues finding references while working on D365 F&O implementation(s).This should be considered for sure.

Category: Development

M

Really need this feature, as it was in AX 2009 and AX 2012. In D365, I can just look at the references, but no way to find out if it is a write or read. Sometime, we are just interested in finding out the write references but not read, so currently I have go through all the references to find out all the write references.

Category: Development

M

Metadata search sort-of helps here, but it would certainly be nice to have more comprehensive and flexible x-ref

Category: Development