There are a lot of different blog posts and video reviews of features available as a part of the Dynamics 365 2020 Wave 1 release. I played with this release a bit and found 2 client-side code enhancements that can be interesting (or even useful) for developers.

I wrote that Xrm.Navigation.navigateTo can be used to open Html web resources in modal dialog in my previous post. As a part of the new release there will be the possibility to open the record in a similar manner. The following code opens the account record in a modal window:

Xrm.Navigation.navigateTo({
		pageType: "entityrecord", 
		entityName: "account",
		entityId: "cf84d93a-3b5a-ea11-a811-000d3a5a1e46",
		//don't pass anything to entityId if you want to create new record
		formId: "B053A39A-041A-4356-ACEF-DDF00182762B"
		//formId parameter is optional. If you want to open particular form
		//you should pass form id inside
	}, 
	{
		target: 2, //2 - to open record in modal dialog
		position: 1, //1 - dialog in center, 2 - side panel
		width: {
			value: 80, 
			unit:"%"
		}
}).then(function(result) {
	var recordReference = result.savedEntityReference;
	//recordReference has the same structure as value of lookup field:
	//[{
	//	id: "cf84d93a-3b5a-ea11-a811-000d3a5a1e46",
	//	entityType: "account",
	//	name: "Record Name"
	//}]
});

One issue I found here is that when the dialog is closed using “X” button, or the record is deleted using “Delete” button from command bar – the promise will remain unresolved so there is no way to handle these scenarios at the moment. Source information is available here – https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/customize-entity-forms#open-an-existing-record

The second interesting feature introduced is the possibility to override the “onclick” event on the record selected in lookup. Default behavior – app navigates you to that record. Now it’s possible to cancel that event or override the behavior. Here is the code:

function onFormLoad(executionContext) {
	var formContext = executionContext.getFormContext();
	
	var lookupControl = formContext.getControl("lookup");
	
	lookupControl.addOnLookupTagClick(onLookupClick);
}

function onLookupClick(executionContext) {
	//to cancel navigation event you can just call following code
	executionContext.getEventArgs().preventDefault();
	
	//to get entityreference of record from lookup you can use following code:
	var recordReference = executionContext.getEventArgs().getTagValue();
	//structure of object is following
	//{
	//	id: "cf84d93a-3b5a-ea11-a811-000d3a5a1e46",
	//	entityType: "account",
	//	name: "Record Name"
	//}
}

More information about this event is available here – https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/events/onlookuptagclick

I thought that it would be really cool to combine those 2 pieces together to override behavior of the lookup item click. Here is the code for it:

function onFormLoad(executionContext) {
    var formContext = executionContext.getFormContext();
    var lookupControl = formContext.getControl("parentaccountid");
    lookupControl.addOnLookupTagClick(onLookupClick);
}

function onLookupClick(executionContext) { 
	executionContext.getEventArgs().preventDefault();
	var recordReference = executionContext.getEventArgs().getTagValue(); 

	Xrm.Navigation.navigateTo({
		pageType: "entityrecord", 
		entityName: recordReference.entityType, 
		entityId: recordReference.id
		}, { 
		target: 2,
		width: { value: 80, unit:"%" } 
		});
}

The following screen capture demonstrates the result: