In Pipeline Builder, we can review a dataset by clicking node.
When we click a column, we can chose the action from popuped menu.
After chosing “filter” , there is a input field to input keyword.
However if we input Japanese key, input field is disapeared soon.
So we can’t use filter in Japanese.
As countermeasure, we write keyword in notepad and copy&paste to input field.
But it is not useful for us. We hope inprovement.
It is difficult to add my situation’s image due to our security, Sorry for inconvenient.
I work with japanese data, and haven’t been able to replicate your issue.
Just out of curiosity, have you tried a different input method in your Operating System?
If you are copy/pasting the text in - and pulling it through Notepad works - it might be a formatting issue. Try to see if you can paste it without formatting pressing CMD + SHIFT + V (Mac) or CTRL + SHIFT + V (Windows).
Hi, jakehop
Thank you for your reply and sorry for late my reply.
I tried paset without formatting, then it is OK to past. We use Windows 11 Pro.
However we can’t input Japanese into input field directly.
It is not useful.
So I was surprised at your situation(no replicate in your enviroment).
I’ve discussed this with a colleague from Japan, and got to play around on their computer for a bit.
I think your next step is to figure out whether you’re using Kana or Romanji input.
If you’re using Microsoft IME, there’s an option to do it - there’s also some key combinations allowing you to switch quickly. I can’t add the link, but search for ‘Microsoft Japanese IME’ for a guide.
Thank you for bringing this issue to our attention. We have identified an issue with the input field you mentioned. We did not properly handle the input of Japanese characters and assumed that any press of the “Enter” key should close the input and filter the table. I believe this is the issue you have encountered.
We have pushed a fix for this issue that will roll out in the next 1-2 weeks. We are also working on preventing these types of issues in other parts of the product going forward. We appreciate your patience, and thank you again for informing us of the issue.
If you still experience this issue in a couple weeks, you can reply here and we can look into other possible causes. Alternatively you can try the solution mentioned by @jakehop.
Thank you for your comment and support.
Just before, I tried again.
However it was not improved yet.
I believe that you will solve this problem in this month.