Dynamically show/ hide buttons on entity list grid in Power Pages portals based on logged in user

(1) Share

Report

Posted on by VM-10031117-0

I'm trying to filter a Power Pages (Power Apps Portal) entity list by the currently logged-in user. Hardcoded fetch XML works, but when I switch to a dynamic approach with Liquid, it fails to filter.

For example, the following hardcoded fetch works fine:

<fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="false">
<entity name="request_ticketlist">
<filter type="and">
<condition attribute="ticket_createdby" operator="eq" uiname="John" uitype="contact" value="{3AAAAA7C-BD8B-EF21-AC21-000D3DDA56F5}" />
</filter>
</entity>
</fetch>

However, when I try referencing the current user’s GUID, it doesn’t work. For example:

{% if user and user.contactid %}
{% assign currentUserId = '{' | append: user.contactid | append: '}' %}
<fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="false">
<entity name="request_ticketlist">
<filter type="and">
<condition attribute="ticket_createdby" operator="eq" value="{{ currentUserId }}" />
</filter>
</entity>
</fetch>
{% endif %}

I’ve confirmed the table permissions for “request_ticketlist” and “ticket_createdby” are correct, and the user is signed in.

Things I’ve tried:

Using {{ user.contactid }} directly without braces.
Checking entity permissions for the contact and request_ticketlist tables.
Verifying sign-in and verifying that “user” data is available in the same block.

Question:
How can I ensure that my fetch XML dynamically filters records based on the signed-in user’s contact ID? Any configuration steps I might be missing?

Thank you!

Note: I used this tutorial to help me (https://debajmecrm.com/how-to-dynamically-show-hide-buttons-on-entity-list-grid-in-powerapps-portals/)

Categories:

Customize & extend

I have the same question (0)

All responses (3)

Answers (0)

RK2021 91 on at

Like (0)

Report
Copy link

Link copied!

Hi - are you placing this code in the same field as on the tutorial, the XML filter?

Was this reply helpful? Yes No
Suggested answer

oliver.rodrigues 9,425 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi, first thing here I would check your table permissions, doesn't it make sense to only allow users to see their own tickets?

If that's what you are trying to achieve, you can define that at the permission level instead of the fetchxml level, this will ensure your data is proteceted

if you still need the permissions to be global for some reason, try using {{ user.id }} to retrieve the user id

Was this reply helpful? Yes No
Suggested answer

Fubar 8,487 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

As per the first response, please specify where you are trying to use the code. If it is in the Filter Criteria field in the screen shot in the link you provided, that field will only accept a hardcoded fetchxml condition - it will not perform additional Liquid commands.

As per Oliver's response, the options for the List are sensitive to the users table permissions so having the correct Scope (Contact, Account, Parent, Global) for permissions may be what you need e.g. if the user doesn't have edit permission on the target the edit option will not show, so having a Lookup on the target record set to the portal users Contact record and a Table Permission (for the target table) with Scope = Contact would probably work.

Was this reply helpful? Yes No