Hey guys,
It's my first post here and English is not my main language so please excuse some spelling and mistakes. Ive got a problem with access just recently. I often use the "Filter Array" function for quick filtering for special words, values and so on. About a month ago some of my flow didn't work quite right.
These flow use the "Filter Array" to filter out some files out of a library with the help of the item ('{Name}') property. So my basic filter function looks like this:
So now the problem..
These files, mostly contain umlauts like ä, ü, ö. If I write these strings like "A- Büro" myself inside the filter Array it work like I used to. (Pic 1)
Buuuut if I get these filenames right out of the trigger body () it doesn't work (Pic 2).
Maybe it is some localization failure?
I tried to replace () these umlauts, but I don't work.
Some got the same or similar failure?
For testing you could add 2 compose actions and put in one the left side of the condition and in the other one the right side. Then you can see what it tries to compare.
I had the exact same problem and in the end solved it like this. Your action "Get files (property only) also has a hidden property called Link or Link to item. Luckily it is already in UTF-8 compatible format. "büro.xls" will be written as "bu%CC%88ro.xls". So I already have a UTF-8 compatibel string for the left side of the filter array. For the right side, all I needed to do is to replace all umlauts (and other special characters with the UTF-8 equivalent. For this I created two arrays at the start of my flow. One to hold the umlauts (including a space, which should be converted to %20). And another one of the same size for the UTF-8 encoded equivalent.
Before doing the filter array, I needed to clean up the search string with a loop that iterates over all special characters and replaces all illegal characters.
Hey,
Thanks for your reply. I will test it.
I wasn't wrong that it worked earlier, was I?
Hey,
I already did that. The Output was, like I thought, the right String. I Guess the Backend does have another view of the variables. 😕
Please mark my answer above as "Accept as Solution".
User | Count |
---|---|
22 | |
15 | |
14 | |
10 | |
9 |
User | Count |
---|---|
43 | |
28 | |
25 | |
24 | |
23 |