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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Supply chain | Supply Chain Management, Commerce
Suggested Answer

"Query has invalid datasource" error when creating production orders

(4) ShareShare
ReportReport
Posted on by 71
 
While creation of Production order getting following error. 
 
 
This was working fine till last week and suddenly started to get this error. The build I am using is 10.0.44
Anyone have any idea on this? 
I have verified all my setups twice and the same thing is working in lower environments.
 
Rajashree
I have the same question (1)
  • André Arnaud de Calavon Profile Picture
    300,911 Super User 2025 Season 2 on at
    Hi Rajashree,

    Are you aware of a recent change in this environment? Are you using Saved views on this form? Do other users also have this same issue?
  • Sohaib Cheema Profile Picture
    49,438 User Group Leader on at
    I have checked it on a few networks, no where this has been reported. Many customers are already using 10.0.44, as the next version 10.0.45 is public as well. 
    If this was an issue, it could have been in posts.
    I can reckon only two thinngs,
    1) it may need an update to next PQU
    2) it may be a usage data thing
    What version are you on?
    do you have saved views on this form?
    Is your form customized?
  • Suggested answer
    DAnny3211 Profile Picture
    11,397 on at

    Hi,

     

    The message “Query has invalid datasource” when creating a production order is typically triggered by one of the following in D365 Supply Chain/FO:

     

    1) Saved view / personalization conflict on the Create production order form

     

    • A saved view can inject a stale or conflicting query for the page and cause “invalid datasource” errors. Try:

      • Switch to the Standard view (view selector), then try again.

      • Clear personalizations for the form (User options → Personalization → Clear for this page) and re‑open.

      • If your org publishes views, ask an admin to temporarily unpublish the view for this form to test.

        Saved views can override the default query and sometimes conflict with pages that already preload filters; Microsoft documents behavior and known caveats for saved views. [1][2]


    •  
     

    2) Usage data or cached query corruption

     

    • Clear Usage data (User options → Usage data → Clear). Several similar list‑page query issues are resolved by resetting usage data. (Community threads frequently point to usage data when a problem reproduces only for some users.) [3]


    •  
     

    3) Recently added form/query extensions or security differences in PROD

     

    • If you recently extended a form or added a data source to a query, ensure the form data sources match the underlying query the form/menu item uses, and that joins/links are valid. Mismatches or added data sources in extensions can throw “required/invalid datasource” errors; also check that the same extension build is deployed to this environment and compiled/synchronized. [4][5]


    •  
     

    4) Menu item / query differences between environments

     

    • It can work in lower environments if the menu item there doesn’t carry a query, but fail in another environment where the menu item (or a cue/related menu) still references an older composite query. Compare the menu item and query artifacts across environments and refresh the form’s query binding if it was modified. [6][7]


    •  
     
     

    Quick triage checklist

     

    • Open the form, select Standard view → retry. If OK, the issue is the saved view; rebuild/publish a clean view. [1]

    • Clear usage data and retry. [3]

    • Test with another user or a test account (different role) to rule out role‑published views and security differences. [1]

    • If you have recent customizations, verify the form/query extensions: added data sources, link types (Join vs Link), or event handlers that alter the query. Ensure the query contains the data sources the form expects. [4][5]

    • If this started after a platform update, install the latest quality update (PQU) for 10.0.44 or consider updating to the next version, as suggested in similar cases. [3]


    •  
     

    If the error persists after these steps, capture a short trace of the failing action and check the infolog/exception stack in the browser developer tools; then compare the Create production order form behavior across environments with identical users/roles.

     

    If this helps resolve the issue, please validate the reply on the thread so others can find it.

     

    Thanks and best regards,

    Daniele

    Note: This response was prepared with support from Copilot to ensure clarity and completeness.


    References
  • Suggested answer
    Rajjos Profile Picture
    71 on at
    Hi All,
     
    @ : I have tried this way but it dint worked so asked the technical team to look into  it.
     
    Thanks for all your replies. There was minor mistake done in backend when duel write was used by our technical team. And feature related to Dual write was got enabled mistakenly. This is what observed and fixed by the technical team. 
     
    Thanks 
    Rajashree
     
  • Suggested answer
    Sagar121 Profile Picture
    827 on at
    This is very common problem, if your envrionment have dual write mapping enabled. Mostly these errors come due to data mismatch between D365 and Dataverse.
     
    Common solutions and best pratices are:- 
     
    After every refresh make sure data sync is completed.
    Changes to mapping should be done in dark hours or when system is alone.
    Try to put monitoring system that count data of D365 entities and Dataverse tables.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Supply chain | Supply Chain Management, Commerce

#1
Siv Sagar Profile Picture

Siv Sagar 266 Super User 2025 Season 2

#2
Laurens vd Tang Profile Picture

Laurens vd Tang 213 Super User 2025 Season 2

#3
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 140 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans