From the Microsoft Dynamics 365 CRM Blogs: Filtered lookup dialog; Elastic tables; Field mappings; Send a customer case

In this week's Microsoft Dynamics 365 CRM blog roundup:

• How to resolve the filtered lookup dialog challenge in on-premise Dynamics CRM using Xrm.Utility.lookupObjects script
• How to make elastic tables in Dynamics 365 CRM
• Dynamics 365 field mappings to quote, order, and invoice
• Dynamics 365 – send a customer case with Azure SMS

How to resolve the filtered lookup dialog challenge in on-premise Dynamics CRM using Xrm.Utility.lookupObjects script

An author writing on the Inogic blog stated that as part of the company’s ongoing work, they actively engaged in developing and deploying one of their products. The author stated that one of the primary objectives is to make it fully functional in an on-premises environment.

However, during this process, the author explained that the team encountered a significant issue while executing an HTML page on the on-load event of one of the entities within Dynamics 365 CRM. The problem: a particular script path crucial to the operation was unavailable.

In the blog post, the author provided a detailed breakdown of the scenario:

On an HTML page, we have incorporated a lookup field. This lookup field is designed to display selected entity lookup records when the user clicks on the navigator image associated with it. However, our current predicament is that it fails to exhibit the expected behavior in the on-premises environment.

The author then provided more context into the issue, saying that the script path reference they included in the HTML page for executing the Xrm.Utility.lookupobjects(lookup parameters) API worked perfectly in D365 CRM online environments but not so much for the on-premises environments.  The author noted that this is causing a major challenge to the company’s deployment efforts. And until the issue is resolved, they offered a workaround.

How to make elastic tables in Dynamics 365 CRM

Another author writing on the Inogic blog noted that elastic tables are a new feature in Dataverse and they come in four types: standard, activity, virtual, and elastic tables. The author stated that elastic tables are designed to handle data that changes a lot. In this blog post, the author discussed elastic tables, which are still in preview, and demonstrated how to make them using code. The author also explained why you might need to use elastic tables.

In addition, the author clarified several important points before getting to the code, including the fact that since elastic tables are still in the testing phase how they work might change in the future. The author then explained how to create an elastic table programmatically and pointed out that elastic entities offer a valuable solution for users dealing with unpredictable and irregular data.

Dynamics 365 field mappings to quote, order, and invoice