Dynamics AX 2012 R2 - dynamically change the preview area based on the selected record

I have a problem that I'm trying to solve, and I'm really not sure if I A) solve it correctly and B) be able to do what I want.

I have a list page which is basically a pivot table (transport table) that has an entry in it for every sales, purchase, and transfer order we ship. With him - a heap of collapsed information and such a common from three sources. We use this table on several list pages and link to where we need it. This was all built by someone else, but I am maintaining some of the parts around him.

I got a request to have a preview pane on a list page based on a pivot table to display rows from source. So, if "sales order" is selected in the grid, display the lines in the preview area for the "sales order" that was selected. Ditto for purchase order and translation order.

So my idea, based on pure ignorance and little experience with Dynamics, is that I would just change the preview area based on the source code. For example, SalesTableListPagePreviewPane has already been updated to work with binding to this PivotTable. So, I wanted to just change the reference to the part at runtime.

I managed to get the FormRun in the list page interaction class from the datasource. I was able to get the list of parts through the PartList object. But I have no idea how to proceed with replacing the part reference.

Am I on the right track? Is this a completely wrong Dynamics AX model?

+3


source to share


1 answer


Your assumption that you can dynamically (runtime) change parts of the form is wrong.

List sheets are especially static, the only code available through interaction classes. This has the advantage that the list can be easily deployed to the Sharepoint Enterprise Portal.

You have several options:



  • Use 3 different page lists for each type of transport.
  • Use a general relationship table with three sub-tables (Sell, Buy, and Transfer).

The last option will allow you to make an outer join on 3 sub tables. The general relationship table might be pooled, but I doubt it will work well.

+1


source







All Articles