Best approach to Historical Product pricing

(0) Share

Report

Posted on by Tango

1,168

Hi,

I am creating a Model Drive Power App (with a lot of the Dynamics crm tables that has a use case where product pricing regularly changes but need to become permanent for a particular quote, job, Invoice and purchase order.

The same product could then be a different price on the next order but when looking back in history, need to see what its price was on an each quote, job, Invoice and purchase order.

So its not the product table but all the other entities that will pull the price in to their tables.

Hoping to get some advice from the experts as to the best way to approach this

Thank you

Todd

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (1)

Sort by

Verified answer

Drew Poggemann 9,287 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Hi @Tango ,

There are a number of things you can do here to track this...

1. Link the Product as a lookup to the Quote Line, Job Line, Invoice Line, etc. so the link is there to the product and can be used in the "relationships"

2. Store the price of the product on the entities that are using them so that it stays consistent on these entities. You could even store multiple fields including the product list price, discount price, etc. on each of these. The key thing is you are storing a separate field than the product price on these entities.

3. You can enable auditing on the Product entity itself and specifically the price field you are wanting to track. This will provide you a history of the price of the product over time. Note, normally the pricing will come from price lists and discount lists etc. vs. the actual product so depending on what you are trying to do here this can be more complicated.

Overall if you copy the price to each of these entities at time of creation (or time of activation / close / etc.) based on your business case then this price will stay consistent on those entities and not change as you change the price of your product over time. You can keep the link so you can then create reporting (maybe Power BI 😀) to analyze the pricing historically...

Was this reply helpful? Yes No
Tango 1,168 on at

Like (0)

Report
Copy link

Link copied!

Thank you @dpoggemann

Was this reply helpful? Yes No