web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Pages / Portal metafilter - fe...
Power Pages
Unanswered

Portal metafilter - fetchxml

(0) ShareShare
ReportReport
Posted on by

Hi all,

I've been putting together some fetchxml metafilters and the following one used to work for any text string (%value%). However, something has changed somewhere, and the opening wildcard no longer works. Does anyone have any ideas?

 

 

<filter type="or" adx:uiinputtype="dynamic" adx:uiname="Organisation">

<condition attribute="organisationidname" value="%%" operator="like" adx:uiinputtype="text"/>

</filter>

 rendered with:

{% if filter.label =='Organisation' %}
<li class="entitylist-filter-option">
<div class="input-group entitylist-filter-option-text">
<label class="entitylist-filter-option-group-label h4" data-filter-id="{{ filter.id | h }}" for="{{ filter_element_id }}">
{{ filter.label | h }}
</label>
<input class="form-control" type="text" name="{{ filter.id | h }}" value="{{ option.text }}" id="{{ filter_element_id }}" />
</div>
</li>
{% endif %}
Categories:
I have the same question (0)
  • oliver.rodrigues Profile Picture
    9,368 Most Valuable Professional on at

    Hi, I am just not sure about the syntax in your fetch/filter.. I believe you need to add the fetch header as well (entity details etc)

    Take a look at this to see if it helps: http://oliverrodrigues365.com/2020/04/26/power-apps-portals-entity-list-conditional-action/

    I am not aware of any changes from Microsoft on that area, if it doesn't work you will probably have to open a ticket with Microsoft

     

  • Community Power Platform Member Profile Picture
    on at

    Thanks Oliver, its an odd one as the filter works fine more or less - the second % wildcard does what it's supposed to and a manually input '*' in the text field works as the 1st wildcard. My problem is that I don't want users to have to use a manual wildcard. I think it's somewhere in the ?mf string parsing, but I'm not quite sure why...

     

  • oliver.rodrigues Profile Picture
    9,368 Most Valuable Professional on at

    Are you rendering your Entity List via custom Liquid? 

    I remember in the past adding a JavaScript to include the * whenever a user triggers the search

    the idea is to add the * in the beginning of the search term, and then when the page loads, you validate that and remove the * if it's present

  • Community Power Platform Member Profile Picture
    on at

    Thanks Oliver,

    I'm using standard(ish) rendering:

    {% entitylist id:page.adx_entitylist.id %}
    {% entityview id:"6c5705db-e507-eb11-a813-000d3a7f5de9", search:params.search, order:params.order, page:params.page, pagesize:params.pagesize, metafilter:params.mf %}
     
    I was thinking around the JavaScript, but it is *not* my area of expertise? Do you have any ideas about how I would do it? It probably plays into a different problem I have as well, where the input data clears of the metafilter boxes on submit.
     
    Ralph

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

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Pages

#1
Jerry-IN Profile Picture

Jerry-IN 71

#2
Fubar Profile Picture

Fubar 62 Super User 2025 Season 2

#3
sannavajjala87 Profile Picture

sannavajjala87 31

Last 30 days Overall leaderboard