Kinetic Dashboard Chart Publish/Subscribe -- CallContextBpmData.xxx Parameters Clearing

Kinetic ERP
21

Adding a BAQ dataview from the wizard showed. :thinking:

22

And now itā€™s working with a manual BAQ dvā€¦ :dumpster_fire:

23

This whole thing is a hot mess. EDD sucks anyway.

It shows deleted dataviews lol.

24

Well, I got it to subscribe to a BAQ dataview, it appears on the list.

But it doesnā€™t work correctly lol.

If its set to filter to >= 2024 and <= 2026 it only shows 24 and 26, but no data from 25

This seems to be the crux of the issue. I was hoping for a simple fix, as the CEO pointed out the issue. I donā€™t have the time to get an entirely separate graphing method figured out :grimacing:

25

Yeah looks like the slider is defined in main.js so not editable in AppStudio. I wish theyā€™d stop doing this and pull those out into apps or /shared. This having the slider in AppStu would be handy so we could fix the columns list and for setting design time pub/sub on our own ep-embedded-app components.

Further, the columns list in the drop down calls the widely used getViewsAndColumns() method which has 3 paths:

  1. BAQ: view schema is baq, so the runtime treats the view as BAQ-backed and resolves columns from the BAQ metadata.

  2. ERP: view schema is Erp, so it resolves columns from ERP class attributes. If the class lookup fails, you get no base column list, so nothing surfaces.

  3. Well-known: special views like CallContextBpmData, CallContextClientData, and Constant bypass metadata lookup and use the live design-time row from current.view(...).dataRow().

There is no path for a dv having blank schema value which is the case for TransView on ootb apps and if you add your own TransView, itā€™ll be schema ā€˜Erpā€™ or ā€˜Iceā€™ so it fails on path 2 beacuse thereā€™s no BO Erp.TransView.

Adding TransView to well-known list doesnā€™t work because thereā€™s no row at design-time.

Thereā€™s also an issue where custom columns go in additionalColumns array and no path handles those.

So custom dataviews and columns are pretty useless. I believe this finding likely relates to a bunch of issues around column inheritance in the framework. Your columns are just not there unless backed by a BO or BAQ. Shame.

EDIT: an ok workaround, as suggested by Kevin, is to set TransView to something generic like Ice.UD01 then use those columns instead of your own. Havenā€™t tried the pub/sub but pretty sure itā€™d work.

image
image1075Ɨ767 26.5 KB