Using Row Filter in combo editor in grid column

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

  1. “PkgControlHeader.JobNum_c = {LaborDtl.JobNum}” - based on the help. This does not do anything. Shows all records for all jobs
  2. “PkgControlHeader_JobNum_c = {LaborDtl.JobNum}” . Used the BAQ format for the field name. Shows all records
  3. Tried a hard coded value: PkgControlHeader_JobNum_c = ‘0000000000000634’ - shows no records. This PCID is linked to the job
  4. PkgControlHeader.JobNum_c = ‘?[LaborDtl.JobNum]’ from a post on this forum. Shows all records
  5. PkgControlHeader.JobNum_c = ‘?{LaborDtl.JobNum}’ Shows all records
  6. PkgControlHeader_JobNum_c = ‘?{LaborDtl.JobNum}’ Shows all records
  7. PkgControlHeader_JobNum_c = ‘?[LaborDtl.JobNum]’ Shows all records
  8. JobNum = ‘?[LaborDtl.JobNum]’ - Thought using the parameter name would work. Shows all records.
  9. @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!

Changing the where list in the provider model did not work either - that has worked for me before

Grid Model->Provider Model → BAQ Options

PkgControlHeader_JobNum_c = ‘?{LaborDtl.JobNum}’

Changing the append filters in reusable combo resulted in no records returning - I expected that. I am using a BAQ not the reusable combo BO’s.

PkgControlHeader_JobNum_c = ‘?[LaborDtl.JobNum]’

I put a read only text box above the Co-Parts grid - LaborDtl.JobNum is indeed the field I am looking for. So I am headed in the right direction.

Hi Tim,
Did you manage to solve this? I am looking to do something similar.
Thanks!
Penny

I couldn’t get the dashboard to do what I wanted so I did something unconventional.

I had a button call a server function to get the next unused PCID return that value.

The condition widget checks if the success response parameter is good.
“{actionResult.success}” === “N”

The next widget (row-update) updated the PCID column (UD field) on the selected line.

Lastly, I made a rest call to force the labor line to update. This would save the PCID on the line, otherwise if someone went to another line they could potentially use the same PCID. Saving it took it off the unused list (which is just a BAQ that lists PCIDS not linked to Time and Expense lines).

Have to admit the experiences with Kinetic dashboards are not good. I wouldn’t regard this as a finished product yet. However at the last webinar Epicor bluntly told me they would not delay getting rid of Classic so here we are :frowning:

So just for info, I fixed my issue by creating a dataview from the BAQ, and using this post from @cbrown (thank you Carol!) to help configure the combobox in the grid against the dataview.

I made the dataview for my combobox a child to the grid dataview, which sorted the filtering nicely.

It is definitely a bit of a learning curve!

1 Like

Thank you! I will try this out the next time I use a combobox on a grid

1 Like