You’re offline. This is a read only version of the page.
19
Hi All
Got a strange issue today where the Inventory on-hand by warehouse V2 entity has set the AVAIALBEONHANDQUANTITY and ORDEREDQUANTITY to zero for all products. In the system the information is displaying correctly, just when you export to either a Datalake or an Excel sheet.
I have been happily exporting this table without problem for a few years.
Has anyone had this happen before? I need these columns for a PBI report so would appreciate any help.
**************UPDATE*********************
Incase anyone else has this issue, it was caused by a caching error on the entity itself.
Hi
Yep tried a new export job, tried republishing the entity to the data lake both which were unsuccessful. We have noticed that the staging table seems to be caching and after a quick test of changing the date on one of the rows we found that the data pulled through to both the Excel export and the data lake.
Have you any suggestions on disabling caching on entities?
Hi Charlotte,
Have you tried creating a new export project? Do you then still have this issue? As I'm not aware of your situation, I would not be able to guess what might be different between your production and UAT environment.
Hi
No changes to the environment since the last update was run in around 8 weeks ago. No customisations to that entity that I am aware of either.
The wierdest part is that our UAT environment (which holds the same data, same versions etc.) seems to be working fine.
Hi Charlotte,
Do you know if there was any change to this environment? E.g. deployed a Microsoft version update and/or customizations?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
290,451
Super User 2024 Season 2
#2
Martin Dráb
228,353
Most Valuable Professional
#3
nmaenpaa
101,148
Share
Report
All responses (
Answers (