Skip to main content

Notifications

Announcements

No record found.

Finance | Project Operations, Human Resources, ...
Suggested answer

DIEF - Staging lines "Not Started" status, import project status "Complete"

(0) ShareShare
ReportReport
Posted on by 90
Good day 365 Community
 
In the last weeks some import jobs seem to stop at some point at random times leaving staging lines with an import status of /Not Started/ even though the import job shows it then /actually/ completes. When rerunning the lines, they import again and then the remainder shows as /created/ in the job status. 
 
On initial import the lines are not created at all. Does anyone know why this happens? It happens on different data entities, but a most recent example is Released Products v2. 
 
No deployments were done, I am one of 2 people working in this environment - so not sure if it could be a bug? 
 
e.g. 
 
 
Error InformationSelectStaging to target statusItem number
Results. It is not allowed to set warehouse management information for items that do not use warehouse management processes.
Results. Update has been canceled.
NoErrorP000006439
Results. A negative price or cost has been detected which is not allowed. This can be caused by entering a negative values for either
of these fields (Price, Price quantity, Charges quantity) please correct the entered value so it is positive or zero.
Results. validateWrite failed on data source 'InventTableModulePurch (InventTableModule)'
NoErrorP000045778
No ErrorsNoNot startedP000000100
No ErrorsNoNot startedP000000102
No ErrorsNoNot startedP000000108
No ErrorsNoNot startedP000000121
No ErrorsNoNot startedP000000124
No ErrorsNoNot startedP000000127
No ErrorsNoNot startedP000000146
 
 
Hope someone can help! Thank you
  • Suggested answer
    Kevin Xia Profile Picture
    Kevin Xia Microsoft Employee on at
    DIEF - Staging lines "Not Started" status, import project status "Complete"
    Hi,

    It is possible that the issue you are experiencing with the import jobs in Dynamics 365 F&O is related to a bug or an issue with the data entities. It is recommended to check for any known issues or updates from Microsoft regarding the specific data entities you are importing, such as the Released Products v2 entity.

    Another possibility is that there might be some underlying data or configuration issues causing the import job to stop at random points. It would be helpful to review the error logs or messages generated during the import process to identify any specific errors or patterns.

    Best regards,
    Kevin

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

Congratulations 2024 Spotlight Honorees

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December

Congratulations to our December super stars! 🥳

Start Your Super User Journey

Join the ranks of our community heros! 🦹

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,759 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,468 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans