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 :
Finance | Project Operations, Human Resources, ...
Unanswered

Updating Purchase Price Agreements via API\ Postman also resets the Price Site Id?

(1) ShareShare
ReportReport
Posted on by 131
Hi folks,
 
I've noticed something strange when updating the Entity PurchasePriceAgreements - it also sets the PriceSiteId to blank and you cannot update it back to its previous value.
 
For example in Postman I am performing the below:
 
PATCH: /data/PurchasePriceAgreements(dataAreaId='A123',RecordId=123456789)?cross-company=true
 
BODY:
        {
            /Price/: 2.99
        }
 
And this does indeed update the Price to 2.99.  However, it also sets the PriceSiteId to // i.e. nothing and wipes out the previous value.
 
Even if I perform a PATCH with the PriceSiteId:
 
BODY:
 
        {
            /Price/: 2.99,
            /PriceSiteId/: /Forward/
        }
 
I receive the message:
 
/message/: /update not allowed for field 'PriceSiteId'/
 
Why is the original PATCH also resetting the 'PriceSiteId' field?  All I want to do is update the Price.
I have the same question (0)
  • Martin Dráb Profile Picture
    237,801 Most Valuable Professional on at
    Do you have the same problem with all inventory dimensions?
     
    There is code inside PurchasePriceAgreementEntity that sets an InventDim buffer on import, but it isn't clear to me how it's supposed to work. It refers to InventInventoryDimensionEntityFieldsMapping but the entity doesn't seem to have this mapping. Maybe the entity is indeed wrong and it never sets any dimension.
  • Michael Hutcheson Profile Picture
    131 on at
    I have not encountered this issue with other inventory dimensions.
     
    If this particular entity has this issue, how else am I going to update Prices on Purchase Price Agreements?
  • Martin Dráb Profile Picture
    237,801 Most Valuable Professional on at
    I'm not sure that I understand. You said you didn't have this problem with other inventory dimensions, but your next sentence says that you have a problem with this particular entity, although we didn't talk about other entities.
     
    Don't you meant to says that you "haven't encountered this issue with other entities" instead of "haven't encountered this issue with other inventory dimensions".

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 > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 664 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

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

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 303 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans