cancel
Showing results for 
Search instead for 
Did you mean: 

Ability to deactivate or hide the create new record from a lookup field

There are many scenarios within a model-driven app, users require create privileges on an entity however they shouldn't be able to create a new record via a lookup field. Currently there is no supported method to hide/disable the create new button (see image below) in a lookup dropdown. The only way is by removing the create privilege which isn't be possible because the user requires it for other functionalities. Would be great to have a setting within a lookup field to enable/disable create record similarly to "recently viewed items" and "allow to change views" settings.

 

2020-06-19_11-11-38.png

Status: New
Comments
JBoman53281
Regular Visitor

It's been a while, anyone have a solution for this?

PH53
Regular Visitor

Remove the ability of the user to create new records via security rol

MariusPothmann
New Member

Hi @EricRegnier, this is indeed possible. Please follow the instruction in this blog post:

Prevent New... button on lookup controls in model-driven apps

 

It can be easily accomplished with supported modification on the formXml. But it would be definitely a nice addition to change the behavior from within the form designer.

 

Kind regards Marius

EricRegnier
Super User

This is awesome @MariusPothmann! Did Microsoft confirmed is was truly supported?

MariusPothmann
New Member

Yes, this is supported as the documentation states:

 

Modification of an unmanaged solution file is supported as described in this documentation. 

  • Form and dashboard customization using FormXml.

Source:

Supported customizations for Microsoft Dataverse (Dataverse) - Power Apps | Microsoft Docs

 

JBoman53281
Regular Visitor

Good find @MariusPothmann 👍

alok2k11
New Member

@MariusPothmann ,

I need same conditional based , if my condition true then wanna hide the same.
Can I do that?

EricRegnier
Super User

@alok2k11, haven't found a way unfortunately. Hopefully when Microsoft implements this feature via the Maker portal or SDK, it will be possible via the client api 🙂