Is there a best practice for ‘compound keys’ characters?
Hi @mellerbeck. Our keys are since ever and always concatenated by pipe and I can not confirm having any behavior you are experiencing.
Could you share more details? Have you e.g. tried duplicating the keys in two OTs and only replaced the pipe by underscore to be certain the pipe is causing the issue?
When I start typing 9551
I can see 9551|35932
But as soon as I type 9551|
It can’t find it (even if I type out the whole 9551|35932)
It does the same thing from live preview of functions (different object, it has a date separated key 2025|06|01)
Can you find it if you copy the key, rather than typing it in?
In that case, it might be an issue of how that specific character is stored/parsed or how it might not be the same unicode character you are typing in.
Not saying you can’t use a keyboard, but mentioning this since I’ve seen similar issues happen before in Foundry.
Thank you for reporting this issue. Upon investigation, we discovered a problem with the handling of pipe characters in query strings in a piece of front-end logic shared among a few components, such as the Object Explorer “Suggested Filter” feature and the Functions preview object dropdown. This problem explains the behavior that you are observing.
We have a fix in the works and will provide another update when we have an ETA on when it will be released. So sorry for the frustration here!