I recently encountered an issue where I created a DataView linked to a BAQ. When I retrieve data using the Erp-BAQ widget, the data is successfully pulled, and I can use it in UD events within Application Studio.
However, when I checked the debug log, I noticed that the DataView does not appear in the Application DataView dropdown. Instead, it is being moved to the System DataView dropdown. I’m unsure why this is happening.
If anyone has encountered this issue before or knows the reason behind it, I would really appreciate your insights.
You are absolutely right. I wouldn’t have been concerned if it were working correctly. However, the issue is that I am trying to populate this DataView via a BAQ.
During a transaction, a series of customized events run, including the ERP-BAQ, which successfully populates the DataView. However, when performing a second transaction, the ERP-BAQ does not populate the DataView, preventing the data from being pulled. That said, when I run the BAQ in the BAQ Designer, it correctly retrieves data.
Strangely, when I refresh the screen, the DataView gets populated with the data from the transaction. I want to eliminate this manual refresh step, allowing users to perform continuous transactions without refreshing the screen.
Upon checking the debug log, I noticed the issue mentioned in the previous thread. I suspect this might be causing the problem, but I am still uncertain.
Since it’s being populated fine the first time, I don’t think your dataview showing up as a system one is the issue.
Do the second transaction with DeV Tools open and after it fails, go to the network tab and look for the ExecuteBAQ call. Is it red? If so, click on it for details.
Thank you for the suggestion, @hmwillett! With the help of DevTools, I was able to locate the issue, and my problem is now resolved. I really appreciate your help!
