{Power 2021} Trigger on save notification only when certain fields change in Model driven App

May 19, 2021 deepeshsomani2013 Microsoft Dynamics CRM

Business Requirement: Show notification in model driven form on save of table only when particular field/attribute has changed.

Solution: In Dynamics 365 , we can achieve this requirement using following script:

// function to show notitification on save
function onSave(executionContext) {
var formContext = executionContext.getFormContext();
var field = formContext.getAttribute(“fieldname”);
if (field.getValue() == VALUETOMATCH && field.getIsDirty())
{
var message = “Field name has changed”;
var messageString =
{
confirmButtonLabel: “Ok”,
text: message
};

var messageAlertOption =
{
height: 120,
width: 260
};

Xrm.Navigation.openAlertDialog(messageString, messageAlertOption);
}
}

Hope it helps and Power 365ing as usual!

Other ways to learn with me:

Any problem in Power Platform or Dynamics 365 – end user, Microsoft partner or an individual?

Problem Area – Technical, Functional, Training, Development or consulting?

Me and my team are here to help, get in touch here: Click here

{Power 2021} Tips for Model driven form design

May 17, 2021May 17, 2021 deepeshsomani2013 Dynamics 365

In today’s blog I will be covering some generic recommendations one should follow while designing Model driven forms.

Ø Review the fields on the form regularly

§ It happens across many CRM deployments over time that certain fields are removed due to business need or are no more relevant to a particular department (Role based forms). Please make sure to remove such unused fields from the form. The lesser the fields, the better the performance as lesser data needs to be transferred over the internet or intranet.

Ø Create different forms for different kinds of departments/ teams/ groups

§ Identify different departments or groupings of individuals in the organization

§ Track the fields that are more relevant to a grouping and consider creating different role based forms.

§ The approach will simplify the usage of form based on relevance to different users and also segregate security requirements.

Ø Avoid unsupported scripting

§ Anything that is not mentioned in Microsoft Docs will be considered an unsupported script. It might be an internal namespace library from Microsoft you are using or DOM manipulation.

§ Try to explain to the customer workarounds to use supported ways of using the form to achieve the requirement.

Ø Mobility considerations

§ If you have needs to use Mobile version of the D365 form, make sure you do proper previews while designing the form to get an idea of how it will appear in D365 Mobile App.

Ø Other Scripting considerations

§ Try to limit onload event handlers, this has a big impact on form load.

§ Use collapsed tabs wherever possible, for example in the case of web resource(html) inside the tab.

§ In case you need to show certain fields based on conditions, keep them initially hidden and then use script to enable them when condition is true.

§ Wherever possible use asynchronous requests instead of synchronous requests.

Ø Usage of sub-grids

§ Not all the sub-grids or related entity data needs to be visible at all times.

§ Try to use and recommend Related tab and Associated grids to the customer wherever related data is needed to be seen which is less frequent to be accessed.

Hope it helps and Power 365ing as usual!

Other ways to learn with me:

Any problem in Power Platform or Dynamics 365 – end user, Microsoft partner or an individual?

Problem Area – Technical, Functional, Training, Development or consulting?

Me and my team are here to help, get in touch here: Click here

{Power 2021} Prevent auto save on specific entities in Dynamics 365 CE

May 10, 2021 deepeshsomani2013 Microsoft Dynamics CRM

Business Requirement: Client wanted to disable auto save on certain Sales entities such as Leads and Opportunities so that it is sure that user has completed all the information. On all other entities, client requirement was to keep auto save.

Solution: We have to write a small client-side script and register it on save event of Lead and Opportunity record to achieve this requirement.

Here is the script:

function preventAutoSaveOperation(executionContext)

{

var eventArguments = executionContext.getEventArgs();

if (eventArguments.getSaveMode() == 70 || eventArguments.getSaveMode() == 2) {

eventArguments.preventDefault();

}

In case you are looking for different types that getSaveMode returns here is the complete list:

Value	Save mode	Table
1	Save	All
2	Save and Close	All
5	Deactivate	All
6	Reactivate	All
7	Send	Email
15	Disqualify	Lead
16	Qualify	Lead
47	Assign	User or Team owned tables
58	Save as Completed	Activities
59	Save and New	All
70	Auto Save	All