Dynamics 365 Portal: Button Filter Criteria for logged user...

(0) Share

Report

Posted on by Tim Made

Hi All,

Help! Is it possible to hide/show Action Buttons on forms based on the logged user? I was thinking that injecting the {{user.id}} into the fetchxml entered within the Button's Filter Criteria should work.... but it's not working. It seems the Filter Criteria only accepts fetchxml. Is this correct? The fetchxml works with hard-coded GUID or without the logged user condition but this is needed because different users will have access to the same view. Splitting entity forms/views by user does not apply here. Example: A delegated user must be able to interact with all records but can ONLY SUBMIT his own record.

Here is my current fetchxml with hardcoded GUID:

Tried: <condition attribute="www_contactid" operator="eq" uitype="contact" value="{{ user.id }}" />

No luck!

Thanks in advance for your help!

Tim

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Kalpavruksh D365 CoE 2,545 on at

Like (1)

Report

RE: Dynamics 365 Portal: Button Filter Criteria for logged user...

Hi Tim,

While logging in the portal, contacts are configured hence you will not be able to get guids of the user table to show/hide button. You can set one flag on Contact and can access that flag value to show/hide button based on the true or false value of that flag.

Was this reply helpful? Yes No
Tim Made 47 on at

Like (0)

Report

RE: Dynamics 365 Portal: Button Filter Criteria for logged user...

Hi Kalpavruksh,

Thanks for your response. Only that this has to be a filter on the logged user. The button toggle is determined by comparing the logged user to the contactid of each record in the Entity List or Form. Hence it will show/hide if there is a match. We can pass the Logged User ID to js in the Custom Javascript area... we should also be able to pass the same to the Filter Criteria of the Action Buttons. Don't know if anyone has been able to do this before somehow. Please heeeelp!

Thanks!

Was this reply helpful? Yes No
Suggested answer

Nicholas Hayduk 2,863 on at

Like (0)

Report

RE: Dynamics 365 Portal: Button Filter Criteria for logged user...

Hi Tim,

Unfortunately I don't think this is possible.

As you pointed out, it doesn't look like any Liquid code within the FetchXML is evaluated.

Another possibility that may have worked was inserting any contact into the query - this works for the filter criteria specified for view, as the Portal code will dynamically replace that ID with the ID of the currently logged in contact, however as you mentioned, that doesn't work either.

Based on what I see in the code, it doesn't look like the FetchXML is processed in any way, except to add the condition of filtering on that specific ID of the row it's looking at (for reasons I mention in my blog post at www.engineeredcode.com/.../dynamics-365-portal-filter-criteria-and-action-buttons). So at this point, I don't think it is possible.

Nick

Was this reply helpful? Yes No
Suggested answer

Ulrikke Akerbaek 5 on at

Like (1)

Report

RE: Dynamics 365 Portal: Button Filter Criteria for logged user...

Hello Tim.

I have implemented a small script that remove the "Deactivate" button for logged in user. I use email address to identify the user. It doesn't work on the Entity Form or List, but on the web page. Remember to add this script on webpages in all languages.

Paste this code into the "Custom Javascript" section of the web page:

$('#EntityFormPanel').on("loaded", function () {

$('.entity-grid.subgrid').on("loaded", function () {

var email = '{{user.emailaddress1}}';

$(this).find("td[data-value='"+email+"']").closest("tr").find(".deactivate-link").remove();

});

});

$(document).ready(function () {

$(".entity-grid.subgrid").trigger("refresh");

});

Was this reply helpful? Yes No