Purchase Order modified/version stamp field

21

Hello,

Just one final follow-up on this - I was able to get the updated code and it will definitely work for us, which is great news.

I wanted to clarify where Quantify will be moving towards in the future in one respect, however. I saw that the VersionStamp was added on the ProductList (and OrderList and SerialNumberList), and accordingly the respective ListItems.

However, the actual objects of each of these do not have the VersionStamp (e.g. Product and Order), whereas other data entities (e.g. Movements) have VersionStamp on both the actual object and ListItem. And other data entities, like StockingLocations, have VersionStamp on the actual object, but not the ListItem.

Is there going to be a standard for where this information will be located in future versions, e.g. on both the actual object on the list item, or one vs. the other, and a recommended approach for retrieving it? I just want to do what I can to make my code future-proof and follow best practices.

Again, this fix will work for us, so not a time-sensitive issue - this is mainly for my curiosity and designing.

Thanks,
Alex

22

Hi Alex.

We made a conscious decision to include the added VersionStamp properties in this release in the List/Item objects.
VersionStamp in editable objects like Product and StockingLocation existed primarily for the benefit of our developers. These may exist independent of the List objects more geared towards the internal usage needs similar to keeping VersionStamp in Product Private as to keep it hidden from specific derived classes.
Going forward, it is planned to expose VersionStamps on all List/Item objects, where one is defined in the database. Also, VersionStampList will be kept to up-to-date for fetching (Primary-Key-ID, VersionStamp) => (Key, Value) in an efficient manner for all tables with a VersionStamp.

Thanks for posting

23

Sounds good, that is all good to know. Thank you for the clarification on this!