Continuing from Part 1: Price Override in Project Operations | Part 1 [Inconsistent Price Update], let’s look at the Pricing.
- When you entered $250 for the Price Per Unit – you assumed it will update the price to $250 from $225
- And what you got it this – $475
Here’s the catch!
Although the wordings of the field convey that it’ll be updated to the absolute price you entered, rather it “added” to the existing Price!!
Hence, 250 + 225 = 475.
So, don’t make the mistake of assuming it’s asking for ‘new price‘, it’s actually asking you ‘how to much to increase or decrease the price by‘
Hope this was useful!
Hope this was helpful!
Here are some Power Automate posts you want to check out –
- Select the item based on a key value using Filter Array in Power Automate
- Select values from an array using Select action in a Power Automate Flow
- Blocking Attachment Extensions in Dynamics 365 CRM
- Upgrade Dataverse for Teams Environment to Dataverse Environment
- Showing Sandbox or Non Production Apps in Power App mobile app
- Create a Power Apps Per User Plan Trial | Dataverse environment
- Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
- Co-presence in Power Automate | Multiple users working on a Flow
- Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
- Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
- Call a Flow from Canvas Power App and get back response | Power Platform
- FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
- Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
- Asynchronous HTTP Response from a Flow | Power Automate
- Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
- Converting JSON to XML and XML to JSON in a Flow | Power Automate
Thank you!