Launch a BAQ Report -- Kinetic Application from Application Studio

jdtrent · February 27, 2026, 9:17pm

Hey,

I have a BAQ report that I’m firing from a Kinetic dashboard. The BAQ report is converted to a Kinetic app and is on a menu.

I’m executing an app-open widget, with the menu name in the widget’s parameters View Name field.

In Launch Options I currently have this (tried different options here):

{
	"value": "='JobAsmbl_CRJobNum_c=' + {actionResult.output} + ';AutoAction=Preview'"
}

JobAsmbl_CRJobNum_c is the exact option field from the BAQ report

{actionResult.output} holds the value I’m passing.

The Value In field is empty, but I’ve stuffed a lot of other things here, too.

When I launch the app, the BAQ report runs and pops up. I just can’t get the value to populate in the option entry on the BAQ report.

Do I need a customization layer on top of the baq report? Is there a better way?

Thanks,

Joe

klincecum · February 27, 2026, 9:24pm

Should that be

{
    "value": "='JobAsmbl_CRJobNum_c=' + '{actionResult.output}' + ';AutoAction=Preview'"
}

?

d_inman · February 27, 2026, 9:24pm

In a customized UD Entry screen I have, I’m opening a BAQ Report with the following in the Value In field and nothing in the Launch Options.

{
	"FormTrackNum": "{UD100.Key1}"
}

klincecum · February 27, 2026, 9:29pm

So maybe..

{
    "JobAsmbl_CRJobNum_c": "'{actionResult.output}'",
    "AutoAction": "Preview"
}

??

klincecum · February 27, 2026, 9:49pm

I think so. I’m looking at one of my BAQ Reports now, and there is no logic in there for processing ValueIn.

jdtrent · February 27, 2026, 11:07pm

Oops. I added a customization layer to the BAQ report and see that the input text box is bound to ReportParam.Option01, so I’ve had the field that we’re filtering instead of the parameter itself in there.

But that didn’t fix the issue.

Here’s what I wound up with on the dashboard side.

app-open parameters:

View Name = Menu name

Launch Options:

{
	"options": {
		"contextValue": {
			"Option01": "{actionResult.output}"
		}
	}
}

Then on the BAQ report customization layer I have an event running After BaseLoad.

Value: “%session.context.initialValueIn.contextValue.Option01%”

Works so far.

Thanks, folks.

Joe