web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Issue with SalesTableListPage → SalesTableDetails Navigation After Adding a Computed Column

(0) ShareShare
ReportReport
Posted on by 185

Hi everyone,

I’m facing an issue with the SalesTableListPage → SalesTableDetails navigation in D365 F&O and would appreciate some guidance.

I have a business requirement to add a Status field that needs to be filterable on the Sales Order List page.

To achieve this, I:

  • Created a View with a computed column for the Status.

  • Added the computed column to the SalesTableListPage.

  • Added the View as a data source to the form query so that the Status field can be filtered.

The issue is that after adding the View to the query, the navigation from the list page to the Sales Order details form no longer works correctly.

For example, if I’m on the list page and click the blue link for Sales Order 250, instead of opening Sales Order 250, it opens Sales Order 1 (or whichever Sales Order is found first).

Interestingly, if I remove my View from the form query, the navigation works correctly again.

So it appears that adding the View/data source or modifying the query is affecting how the selected SalesTable record is passed to the SalesTableDetails form.

Has anyone encountered a similar issue?

Could this be related to the join between SalesTable and the View, the data source relations, or the link/reference fields used for navigation?

I would especially appreciate any guidance on how to add a filterable field from a View to the SalesTableListPage without breaking the standard navigation to SalesTableDetails.

Thanks in advance!


View I created

Query Extension of the salestable list page query:

Categories:
  • Suggested answer
    Assisted by AI
    CU-1234529-002 Profile Picture
    568 on at

    Hi, this is a classic issue when adding a new data source to a list page query  the navigation breaks because the form's record context gets confused about which data source drives the selected record.

    The fix is to check your data source join properties:

    Make sure the View data source Join Mode is set to OuterJoin (not InnerJoin, inner join can filter out records and shift the selected index).

    Set Fetch Mode to 1:1 on the View data source.

    Most importantly, check the LinkType on your View data source  it should be InnerJoin or ExistsJoin depending on your case, but the key thing is the SalesTable must remain the root/primary data source driving navigation.

    Also verify the relation between SalesTable and your View is correctly defined on SalesOrderId/RecId if the join key is off, it picks the first matching record instead of the selected one.

    If the issue persists, another clean approach is to not add the View to the form query at all  instead use a display method on SalesTable that computes the status, and mark it as allowedit(false). It won't need a query join and navigation stays intact, though filtering becomes limited.

    Thanks, 

  • Anton Venter Profile Picture
    21,296 Super User 2026 Season 2 on at

    @CU-1234529-002 

    Is your reply created using AI? It seems to be the case. Can you confirm?

    If or when using AI to answer posts, please remember to enable the "Mark reply as AI-assisted" checkbox before posting so that the source is clear to everyone.

  • BZF_SA Profile Picture
    185 on at

    @CU-1234529-002 What you suggested is what i have already tried and it's not working.

  • André Arnaud de Calavon Profile Picture
    307,747 Super User 2026 Season 2 on at

    Hi BZF,

     

    Can you share screenshots of the properties you have for the form data sources SalesTable and your view? I do see you have a second data source added. Is it working correctly with the second data source?

  • BZF_SA Profile Picture
    185 on at

    Hi @André Arnaud de Cal... ,

    Yes it is working with the other DS. It's only breaks when I add my view as DS. Below are the properties for the View DS and For the view in SalesTableListpage Query It's inner join with dynamics fields set to YES

     

  • martinarul Profile Picture
    233 on at

    Hi BZF,

    Did you write any methods in the form for your customizations to work? I guess its due wrong call of super(), check in that angle. 

     

    Regards

    Martin

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the August Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 543 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 415 Super User 2026 Season 2

#3
CU-1234529-002 Profile Picture

CU-1234529-002 188

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans