Happy to help you with this. Can you provide some more information? I suppose you are doing something with the ICP token or is it for some other ICRC-1 token?
I am surprised to see that the dashboard indeed does not support searching for ICRC-1 account identifiers such as the one you provided: h5boe-vqaaa-aaaam-ac36q-cai-ckw43vy.6867bf53ffcaa0cd11f3bb59be8e4d9e71b20d096cc822a5dffecc7561b026ce.
That is a shortcoming of the dashboard. However, ICP is the exception here. For all other tokens the dashboard supports searching for ICRC-1 account identifiers. So this is something that needs to be fixed in the dashboard.
I suppose the same is true for the NNS wallet. ICP is probably an exception when compared to all other ICRC-1 tokens. And this should be fixed as well.
If this is indeed specifically about ICP tokens then you can convert the ICRC-1 account identifier to the legacy identifier (aka “original account id”). In your case h5boe-vqaaa-aaaam-ac36q-cai-ckw43vy.6867bf53ffcaa0cd11f3bb59be8e4d9e71b20d096cc822a5dffecc7561b026ce converts to 4d986d218bf8eb0473e002caf8b6de660e2ce580834190c71bfc6d7f5e82b78d. Your frontend can convert it for the user.
But some wallets actually support the ICRC-1 account identifier even for ICP transfers. If the NNS wallet does not then it is a shortcoming and should be fixed. The wallet we developed here does support sending any token to ICRC-1 account identifiers including ICP.