SAP Agentry - Indexed search on Complex Table related screen fields

[madan_km]

Hi,

I am using the latest Agentry Editor plugin (73.0.2.20) to develop a customised SAP Work Manager solution. I have come across a specific scenario, which doesn't look correct. Let me explain.

I have a complex table which has a field (No. of Chars = 1). This field mostly gets filled with an annotated character (Eg. Á)

When I mark this Complex table to a Complex Table search edit type field in a screen, I could see this field with right values. But when I have an index created for this field and try to search on this index on a Complex Table Search field, say my search input is ‘Á’, it doesn’t filter rows that has ‘Á’ in that specific field, instead it shows every row that has ‘A’ in that field.

From this, I can see that the indexed search is not considering the annotated characters but just the basic English characters.

This looks like a product bug to me, but any ideas/suggestions to work around this situation will be much appreciated.

Thanks,

Madan KM

[jim_bonczyk]

Madan,

Is the complex table *field* type set to ASCII, Unicode, or Unicode case insensitive? There is a difference in the comparison functions used by each of the types. For your use case, I believe that you will want to use the case *sensitive* Unicode type.

Jim

[madan_km]

Thanks Jim.

I have this Complex table field initially set to 'International String (Case-insensitive)'. But, right after I changed this field to 'International String (Case-Sensitive)', the relevant field's index disappeared from the 'Search Dialog Indexes' section of the Complex table search field. When I changed it back to 'International String (Case-insensitive)', the index reappeared in the 'Search Dialog Indexes' section'.

However, I have managed to set this search index manually as the single fixed search index for the Complex table search field. But the iOS Work Manager Client does not consider this to be a valid index, likely because the mapped complex table field to the index is 'International String (Case-sensitive)'.

When I change the field back to 'International String (Case-insensitive)', things work normally. The Complex table search opens up.

Madan KM