Solved

Allow wildcards in the PF step Change filter

  • 8 January 2024
  • 5 replies
  • 86 views

Userlevel 5
Badge +12

Hi, 

I have a task for searching something.

Start Task from menu. Enter value (shipment number), open document - start empty, change filters.

When I enter the exact value it works ok. Open the table and show the row. 

For example: Shipment number: 22fe0530

This will output this query in the debugger: 

as t1
where (t1.[shipment_number] = N'22fe0530')

However, I want people to be able to use the filter similar to ‘ctrl - G Filter’ .

When I set ‘Allow Wildcards’ in my PF step ‘Change Filters’, it still searches for the exact entered value, giving this; 

 as t1
where (t1.[shipment_number] = N'22FE*')

When filtering in the ‘ctrl-G filter’  it outputs; 

 and (t1.[shipment_number] like N'%22fe%')

Which will result in several rows that match. 

The documentation states that the COL value must be EQUAL, so the = makes sense. But then.. What to do with the wildcard?

In short, can it be done to output all rows with Shipment_number like 22fe% - when entering a value in a task and then open the document, and show these rows? 

Thanks! 

Blommetje 

icon

Best answer by Mark Jongeling 5 February 2024, 09:43

View original

5 replies

Userlevel 7
Badge +23

Hey @Blommetje,

This seems to me this is a bug. However, did you try this with Universal too? Just to be sure if it is only an issue with 2-tier Windows GUI or also Universal with Indicium.

Userlevel 7
Badge +23

@Blommetje , have you tried out my suggestion?

Badge

I am experiencing the same issue/bug. This also occurs in Universal.

Userlevel 7
Badge +23

I am experiencing the same issue/bug. This also occurs in Universal.

That is unfortunate, could you create a ticket for this in TCP? 

Badge

Hi Mark,

Sure, will do!

Reply