<@UE3DBP8JC> yes - this is the hack <https://stack...
# suiteanalytics
m
@pmendola yes - this is the hack https://stackoverflow.com/a/37015961/3230114
p
Ahh yes I've seen this before! Just have to figure out how to tweak it for just inventory quantity
m
What do you need to change?
p
I suppose the logic needs to be reversed a bit, basically i want to be able to show a SKU and then show on separate lines in order, the transactions that caused its inventory to go up or down, and the fields on that related transaction
m
That what this but all for a specific SKU - it's a sublist on the inventory item record. But if you wanted to turn it into a report for all skus you could just add a result column for the sku and run it as a search
p
Your right, I think I got it. Thanks!
k
one caveat to all this - inventory is "date" based, but when you look at the records may not be reflective of what users saw when they were entering transactions on that date because of backdated transactions. you might highlight backdated transactions where created date > transaction date so that you can know those things. Also this won't accommodate for when someone delete transactions or edited dates on them. as well. I guess what I'm trying to say here - is take it with a grain of salt.
The final number should net out to what current inventory is - but specific dates along the way are likely to be wrong if internal controls around inventory aren't strong
One last thing - you can't possibly do this with quantity available unless you are smarter than I am with NS Saved Searches. only quantity on hand can be done with this.
p
Good caveats Kevin, I turned this on for them today so as I hear about requests for what else it should show I'll keep that in mind