Finance | Project Operations, Human Resources, ...

Detecting any changes in Avail Physical field in InventSum table

(1) Share

Report

Posted on by CU15021230-0

I want to detect any changes in Avail Physical field in InventSum table in 365.

I used onUpdated event handler but it's not working perfectly as for example after invoice sales line in sales order,it's not execute the event handler so any suggestions to detect every change in this field?

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (8)

Answers (0)

Sort by

Suggested answer

Sankar Ramalingam 262 on at

Like (0)

Report
Copy link

Link copied!

Each IN and OUT inventory activity in InventSum table will be individual entry. So, OnModified wouldn't be helpful for your case. Explain the use bit more to more suggestion.

Was this reply helpful? Yes No
Martin Dráb 239,650 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

InventSum is a special case; it uses some hacks, because it's so important for performance and there are risks of blocking. There are things like InventSumDelta involved. Before going deep into this complexity, please explain the business requirement to us, so we're sure that such a thing is really necessary.

Using OnModified event is a bad idea - it's called when a user changes a field value in UI, which never happens with InventSum, and even if it was, it doesn't mean that the modified field value will be saved.

Was this reply helpful? Yes No
CU15021230-0 64 on at

Like (0)

Report
Copy link

Link copied!

I want to sync with avail physical field in real time any change happened in the avail Physical from whole system I want to detect it

Was this reply helpful? Yes No
Martin Dráb 239,650 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

That's not a business requirement. Please forget your idea about the implementation for a moment and tell us why end-users want to change the application.

For instance, you mention synchronization with something, so maybe users need the information about available quantity on an e-shop or something, so they're able to tell users whether they can order the item. When we have information like this, we can start thinking about the architecture, such as using the Inventory visibility service (instead of any synchronization),

Was this reply helpful? Yes No
CU15021230-0 64 on at

Like (0)

Report
Copy link

Link copied!

Yes, it's something like e-shop,I want to detect any changes happened in the quantity for specific item to reflect to my application to specify whether the customer can order this item or not at real time

Was this reply helpful? Yes No
Martin Dráb 239,650 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

In my opinion, you're making a mistake by focusing on a single solution. You should analyze the business requirements, the available solutions and limitations and chose a solution that meets the requirements and can be implement. It seems that you chose a solution before understanding your options, and you chose something that you can't actually implement.

Was this reply helpful? Yes No
CU15021230-0 64 on at

Like (0)

Report
Copy link

Link copied!

Company x has a physical inventory of a specific items and Company Y has an e-commerce website. Company x wants to sell its own products on company Y's website. Company Y wants to know the exact inventory stock at company X at real time so the e-commerce can make this items available for new orders or not

Was this reply helpful? Yes No
Suggested answer

Martin Dráb 239,650 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

First of all, don't automatically accept what users ask for. It sometimes differ from what they actually need. For instance, users usually want all integration synchronous, but they aren't software architects, therefore they don't think about things like performance and throttling, availability (e.g. should all processes stop if F&O is down for maintenance) and so on. It's up to us to find the actual requirements, even those that users aren't aware of, and design a solution that meets them. It's often quite different from what users originally wanted, but it's (hopefully) much more robust and safer.

If you want to request the data "at real time", then you likely don't want a synchronization. Synchronization has a delay and it's useful when you don't want to make a real-time request every time (but you reuse the synchronized value until the next synchronization).

If asking F&O for the availability every time is the right design for the given requirements, let me again suggest Inventory Visibility Add-in. It's what F&O offers for this scenario. In past, custom services used to be used for this purpose, but the solution from Microsofts adds an extra layer that solves some problems of classic synchronous integration.

Was this reply helpful? Yes No