I'm exploring the capabilities of Ignition regarding filtering and searching functionality within tables, and I would like to understand the extent to which Ignition can handle specific language and case-insensitive requirements.
Requirements:
1.Sorting lists in an alphanumeric French format. The system should account for both alphabetical characters (with accents) and numerical values, following the French formalized format (e.g., fr_FR.UTF-8).
2. Search fields should support searches for words with or without accents (e.g., école and ecole).
3. Case-insensitive searches (e.g., Ecole, ecole, école).
Can anyone confirm if these functionalities are natively supported in Ignition Perspective - Table Filtre, or if custom configurations are required? If possible, could you share any best practices for setting this up using only built-in Ignition components?
I haven't received a response yet. I would greatly appreciate any help or insights on this matter.
Any assistance or suggestions would be greatly appreciated.
Have you got any examples of filtering you are trying and what is happening?
Most people here probably haven't done what you are asking, but if you try it and hit a snag, there is a lot of people here with many many years of experience with the tools that can assist.
A lot of integrators only "know" what they have run into on a job, but if you show them the problems you encounter, they immediately recognise things they might know and can help with.
I have not done multi-lingual systems as I am in a country that is mainly single language.
What I can say is that computers really don't care less what language data is in, as long as it is in a standard format. If all your filtering is done on unicode characters, in the software all characters are recognised just the same way as an english character set, and you will be able to filter all types of unicode using the same tools.
Where you will have issues is where you are expecting the system to automatically recognise two characters as the same letter é and e. This is where you are now asking the computer to compare two things that are not the same but now need to be treated the same. This is now something you need language definitions and plugins to help with.
There are definitely scripts an libraries that can be used to make this work, but their suitability is completely revolving around the context and task you are trying to accomplish. This further reinforces my previous point about sharing what you are trying, what the problem you need to solve is, and what works/doesn't work.
You asked on a Friday and bumped on a Monday (American time, where the majority of the regulars on this forum reside).
I'll also mention that this forum is not an official support venue; there are no SLAs or other agreements here. While some IA staff, myself included, participate, your only avenue if you need a response is our support department officially: https://support.inductiveautomation.com/
As for your questions:
I would not expect the table to handle this natively, but you absolutely should be able to use scripting to achieve this.
I can guarantee that the table doesn't do this natively, but again, you should able to collapse your search term down to a base form via scripting.
I'm somewhat surprised by this, but I don't see a way to do case folding directly within the native table. Yet again, it would absolutely be possible to do this via scripting, but it doesn't appear to be built in to the table.