Skip to main content

Notifications

Dynamics 365 general forum

Unified Interface category search virtual entity missing

Posted on by 1,570

Hello,

We are tying to use a virtual entity with global categorized search.

This works fine in classic interface. But the virtual entities do not appear as searchable in unified interface.

Is there a way to enable this or is it just not available yet from UI global categorized search?

Thank you,

Tom

Categories:
  • Johnny Gong Profile Picture
    Johnny Gong 6,482 on at
    RE: Unified Interface category search virtual entity missing

    Tom S,

    Sorry for the misleading. I mixed mentioned Virtual Entity global search with known Virtual Entity Loopup field issue. I am glad to see the issue resolved by yourselves.

    Have a nice day.

    Regards

    Johnny

  • TomSmelser Profile Picture
    TomSmelser 1,570 on at
    RE: Unified Interface category search virtual entity missing

    JG,

    Thank you for the reply. But I believe you may be referring to other issue where virtual entity will not work in a grid. 

    It seems for my issue that if virtual entity is missing from the App used in unified interface that it will not appear in global search.

    After adding the necessary entities in the app things worked fine.  This is a simple setting/checkbox for the entity within the app config.

    Best Regards,
    Tom

  • Suggested answer
    Johnny Gong Profile Picture
    Johnny Gong 6,482 on at
    RE: Unified Interface category search virtual entity missing

    Hi Tom,
    After the investigation, this is a known bug issue that Virtual Entites LookUp/Categorized search not working in UCI. Returning no values. It works fine in old Web client
    I found the issue is happening for virtual entities but the actual root cause (based on the bug your team created) is actually in the Grids control itself.
    Virtual entities not loaded when they are within a “Unified Interface” based they need multivalue field to be working in UCI grid.
    This bug is closed as won't fixed at 2019/02/01 since the cx owner discontinued this investigation and closed the case. So Dev team does not have plan to address this bug. The left comment said if the scenario still repro and is important enough, please reactivate with additional details and they would re-evaluate this decision.
    If you would like to dig it out, I would recommend to raise a ticket to re-active the bug investigation process.
    Hope the above info could help. Thanks.
    Regards
    Johnny

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,240 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,149 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans