Error after enabling filter on PartNum field in Customer Tracker

A user wants to be able to filter by Part Number in the Customer Tracker > Activity > Orders grid. By default there is no filter on that field when you enable the filter row. So I created a customization to enable the filter on that field and when you enter something in the filter box there is an error. Seems like it should work.. ?

Screens:

Here is the default filtering when you enable the filter for the Orders grid:

Here I am in App Studio and you can see the grid is filterable:

Here is the PartNum column in the grid and I changed Filterable to true:

Here is the screen in preview mode attempting to use the filter:

If you type in the Part filter, error:

And here is the debug window:

There could be something in the debug window that I am not seeing, I am new to that.

Any ideas? Thanks

What is the error detail from the Server Log that corresponds with the correlation error number?

Where do I find that?
thanks

If you’re on prem, you can get it off your app server directly. Though the SaaS method may work for you as well.

If you’re SaaS, then you’ll have to use Server File Download. Select Admin then search and wait for it to populate and find the correct dated log file in appserverlogs folder:

1 Like

Found it - thanks.

OK it looks like this might be the error: Invalid column name ‘PartNum’

Correlation ID’s match up.

Not sure why that would cause the error though.

You should use DataVew_PartNum replace “DataView” with a valid dataview from your layer.

Hmm.. well I didn’t add that column I just made it filterable. And none of the other columns have the dataview in their names.

I know you didn’t add the column. The dataview for that grid is OrderCustTrk so try OrderCustTrk_PartNum.

1 Like

The general rules are:

  1. Column is already filterable if it is a native part of the BO method
  2. If you click the download button :down_arrow: then you can filter anything.
  3. Of course you are limited to filtering the records that you downloaded (say 500). You can override that.
  4. @Mark_Wonsil will soon explain how wasteful that is…

Kind-of hack to this: If POs cannot be filtered by supplier name nor supplier ID (for example), you might find that supplier number (the integer) is hidden but is a default filter. (Been there.)

4 Likes

OK I poked around a little more in the debugging and was able to find the source of the error (I think). It looks like it is querying OrderHed and PartNum is not a field in that table:

I will try your suggestion above.

1 Like

OK, yes after you download, you can filter on any field:

That works!

Thank you both for your help. :slightly_smiling_face:

2 Likes