On a Kinetic Dashboard, 2025.1.5, I have a chart connected to an EDD view.
I have combo boxes bound to two transview fields, the change of which sets the value into CallContextBpmData.Character02 for the input parameter, in this case a single resource group, or Character01, which will contain a comma-separated list of product groups.
The only options I see for the parameter input are CallContextBpmData.xxx, Constants, and query dataview fields, which arenāt useful in this case because of the comma-separated list in Character01.
Anyone have a suggestion about how to either keep the fields from clearing or assign a transview field to the subscriber?
Are you saying add the columns to the CallContextBpmData dataview?
I have the columns defined in the Transview dataview. They are working fine filtering other dataviews.
The problem is that the publish/subscribe setup wonāt take the Transview columns in the Publisher column. The drop-down box has a list that includes call context and constants, but no Transview entries.
I tried typing the transview column name into the list, but of course it wonāt take the value if itās not in the list. Maybe thereās something Iām missing.
Bump for a new week. Anyone have an idea about this?
Again, CallContextBpmData fields that we use for EDD chart filters are being cleared intermittently, seemingly when the process āGetMonitorDataKeepIdleTimeā fires.
The values in the call context fields are coming from fields set into the Transview dataview, but Transview fields are not selectable in the Publisher dropdown box.
Probably the dumb way to do it with Browser-Only on the horizon, but I still go into the client and do my publish-subscribe then complete the rest in App Studioā¦
Is there some other setup needed to first publish your TransView field so that you can subscribe to it? Weāre doing dashboard uplifts now, so Iāll be digging around too
Your best bet is if you need to store them for extended periods, keep them in somewhere like transview. Set them right before the call to wherever. The lifetime of CallContextBPMData is only guaranteed for a single call stack.
Yes, but like @jdtrent mentioned, things like transview are not selectable, nor can you manually type something in. I would have done it that way to begin with if it was allowed.
I was wondering if he found a way to make a custom dataview appear in the lists. I donāt see what is so special about the CallContextBPMData data view.
Have no idea why TransView doesnāt show in the drop down. I wonder if that screen is specifically excluding TransView as I see all the other dvs in the list. Perhaps try creating another dv. I cannot test another dataview atm because AppStu isnāt working.
Alternatively, you could set it in the json capabilities array of the ep-embedded-app component:
I did, did not appear. Strangely, the only ācustomā dataview that appears on the list is the BAQ dataview created by the dashboard conversion wizard.