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 :
Dynamics 365 Community / Forums / Supply chain | Supply Chain Management, Commerce / error in importing PO ...
Supply chain | Supply Chain Management, Commerce
Answered

error in importing PO lines via data management in PU33

(0) ShareShare
ReportReport
Posted on by Rahul Mohta 21,042

I have been importing PO lines however recently started getting error in importing PO lines via data management in PU33

Installed product version : 10.0.9 (10.0.383.20005)
Installed platform version : Update33 (7.0.5559.41422)

getting error as below

Results. update not allowed for field 'PurchPurchaseOrderLineV2Entity.PurchaseOrderNumber'

I have the same question (0)
  • Blue Wang Profile Picture
    Blue Wang Microsoft Employee on at

    Hi Rahul,

    PurchaseOrderNumber field in PurchPurchaseOrderLineV2Staging table is not allow edit.

    Have you tested in other environments？

  • Rahul Mohta Profile Picture
    Rahul Mohta 21,042 on at

    yes did try with other environment and it somehow is coming only this environment

    no code changes

    no definite hotfix on LCS

    reaching to MS support with a case

  • vince.perta Profile Picture
    vince.perta 9 on at

    Have you found a resolution to this?  We recently started experiencing the same issue.

    We're on a slightly different version that you:

    10.0.9 (10.0.383.10010)

    Update33 (7.0.5559.35512)

  • Verified answer
    Rahul Mohta Profile Picture
    Rahul Mohta 21,042 on at

    the fix is to check and remove any Bad data using below query and then import

    SELECT *INTO [purchLineBackup] FROM purchLine WHERE purchLine.InventTransId = " "

  • vince.perta Profile Picture
    vince.perta 9 on at

    Thank you.  We did have one PurchLine with a blank InventTransId, and deleting it resolved this issue.

  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 303,674 Super User 2026 Season 1 on at

    Thanks for the feedback, Rahul. I have marked your answer as verified as you probably can't do it for your own questions.

    So, in fact a missing mandatory field value was the cause for a misleading error message.

  • vince.perta Profile Picture
    vince.perta 9 on at

    I think it's worth pointing out though, that the missing mandatory field isn't on the record being imported that is throwing the error, but rather on a record already in the destination table, preventing any other records from being imported.

  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 303,674 Super User 2026 Season 1 on at

    Correct Vince! I should have mentioned that more clearly.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Supply chain | Supply Chain Management, Commerce

#1
Mallesh Deshapaga Profile Picture

Mallesh Deshapaga 254

#2
Laurens vd Tang Profile Picture

Laurens vd Tang 188 Super User 2026 Season 1

#3
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 131 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Quality order uses default receipt location instead of actual physical receipt location

Product updates

Dynamics 365 release plans