Hello,

We want to disable the ability to use the "New" City/State option in the City/State lookup fields of an address. What is the best way to accomplish this?

Like 0

Like

3 comments
Best reply

Hi Allen Dsouza,

 

This button is displayed if the Lookup has an edit page. If we are talking about a selection card from a lookup, the "getSelectionControlsConfig" method in the "LookupPageViewGenerator" schema is responsible for loading the list of edit pages.

 

There is no instruction, but the "BaseLookupPageV2" schema is responsible for this page \ window, the "Add" button name is: "SeparateModeAddRecordButton", the "ActionsButton" - it's action button. You can replace and customize the visibility of these buttons as you need.

 

P.S. If you have an option to hide it without using code, I'm suggesting you to do it, just by changing "Lookup view" from "Selection window" to "List" and there will be no option to add "New" City/State. (Example attached below)







Best Regards, 



Bogdan L.

Dear Allen,

 

Thank you for your question!

 

The best way to accomplish the restrictions to add new records to a lookup without development would be to update the Object Permissions.

 

Navigate to the [Object Permissions], find there the required lookup, and disable the "Create" option for "All employees" (or for a different group if you are using them):

 

And save. Make sure to "Update the record permissions" in the Action drop-down menu.

 

The result would be like in the screenshot below:

 Hope this helps!

 

Thank you, hope you have a great day!

 

Regards,

Danyil

Danyil Onoprienko,

Thank you for the suggestion! Due to some complex security setup in the system, we are considering using code disable/hide the "NEW" option on the lookup. Is there a way to do this?

Hi Allen Dsouza,

 

This button is displayed if the Lookup has an edit page. If we are talking about a selection card from a lookup, the "getSelectionControlsConfig" method in the "LookupPageViewGenerator" schema is responsible for loading the list of edit pages.

 

There is no instruction, but the "BaseLookupPageV2" schema is responsible for this page \ window, the "Add" button name is: "SeparateModeAddRecordButton", the "ActionsButton" - it's action button. You can replace and customize the visibility of these buttons as you need.

 

P.S. If you have an option to hide it without using code, I'm suggesting you to do it, just by changing "Lookup view" from "Selection window" to "List" and there will be no option to add "New" City/State. (Example attached below)







Best Regards, 



Bogdan L.

Show all comments

Hi Team,

How to configure control element binded to some text type field (non-lookup field) to works similar to drop-down list ?

 

What i would like to achive:

When user typing customer name system should check existing customers from Account object and suggest choose one of they from drop-down list.

In case when typed customer name wasn't chosen from suggested list or wasn't find system should keep typed value on field (not cleaned it after  changing focus or saving as is functionality of lookup field). 

I would like to implement this functionality on Lead mini-page in creation mode on Account field and Contact field.

 

Regards,

Marcin Kott

Like 0

Like

3 comments

Dear Marcin,

Unfortunately, we do not have any ready examples of the required functionality. However, there is the “To” field in the “Email” tab from Actions Dashboard https://prnt.sc/qon7l5 . This field has the “text” type, can be filled from the lookup and is not cleaned after changing focus. Please take a closer look at this field.

The field is located in the “EmailMessagePublisherPage” schema and has the “Recipient” name https://prnt.sc/qoni6a

 If you have any further question, please contact technical support.

Best regards,

Norton

do you mean like this?

if I'm right, check "AccountMiniPage" Enrichment package and "CompaniesListHelper" for example.

Hi again,

First solution was not enought because i need click on lookup button and search again same text.

Second solution was my thought to, but afraid complexity of modification. But finally decided to go this way and it's works perfect.

Thank You

Show all comments