DESCRIPTION

It is one of the most popular bugs which almost every developer may face during Portal configuration.

It is well-known that if you want to filter the view on Portal depending on the logged-in user or its “Parent Account” value, you simply need to put a single random value in the corresponding lookup attribute in the view filter criteria (See the example below).

Top 5 Bugs on the Microsoft Dynamics Portal and How to Fix Them - View filter criteria

View filter criteria

It will dynamically substitute the logged-in user Contact record instead of choosing one in the filter. Unfortunately, it does not work with the Lookup Metadata filter on Entity List.

WHEN IT HAPPENS

In the example below, you see that you need to provide an existing view instead of filter criteria. However, if you want to use here a view with a dynamic filtration feature – it won’t work.

Top 5 Bugs on the Microsoft Dynamics Portal and How to Fix Them - Metadata filter

Metadata filter of the entity list

HOW TO FIX IT

The only codeless solution you have is to filter records using Entity Permission. However, be aware that it will affect all the pages that use the “Enable entity permission” condition.

Another approach (using code) is to modify filter options using the Liquid+Javascript combination. First will request the correct EntityList for you. Second, will help you to replace options in the filter with the dataset retrieved by Liquid.