We are working on replicating our Time and Expense customization in Kinetic
In short we have a PCID column (PCID_c) on LaborPart and it is populated by a BAQ, filtered by the job number.
This is working in classic on the Co_parts Screen.
In Kinetic I’ve got the column working with the BAQ and it is showing the PCIDs, however it shows all of the records returned by the BAQ for any Job Number.
.
Side note the BAQ itself does have a parameter JobNum - this works outside of Application studio
I’ve tried the following row filters
- “PkgControlHeader.JobNum_c = {LaborDtl.JobNum}” - based on the help. This does not do anything. Shows all records for all jobs
- “PkgControlHeader_JobNum_c = {LaborDtl.JobNum}” . Used the BAQ format for the field name. Shows all records
- Tried a hard coded value: PkgControlHeader_JobNum_c = ‘0000000000000634’ - shows no records. This PCID is linked to the job
- PkgControlHeader.JobNum_c = ‘?[LaborDtl.JobNum]’ from a post on this forum. Shows all records
- PkgControlHeader.JobNum_c = ‘?{LaborDtl.JobNum}’ Shows all records
- PkgControlHeader_JobNum_c = ‘?{LaborDtl.JobNum}’ Shows all records
- PkgControlHeader_JobNum_c = ‘?[LaborDtl.JobNum]’ Shows all records
- JobNum = ‘?[LaborDtl.JobNum]’ - Thought using the parameter name would work. Shows all records.
- @JobNum = ‘?[LaborDtl.JobNum]’ - Thought using the parameter name would work. Shows all records.
Funny thing is that none of these cause errors. The only difference was when I tried the hardcoded value - it just didn’t return anything. All others return all records from the BAQ
The first row already had a PCID in the data - this is showing correctly.
When I use the drop down on any row it shows all PCIDs pulled by the query. No filtering.
Honestly Epicor should make a wizard or provide examples. I see a lot of frustration on the forum when it comes to filters and such lol.
I’ve had a lot of issues when exporting Classic Dashboards to Kinetic especially multi grid but anything that uses the same date column as a date range. So even our simple dashboards that took under a half hour to make require manual intervention for nearly all of them. Oi!

