This article provides step-by-step instructions on how to create a new OData Dialog record as a part of the Lasernet Connector configuration within Microsoft Dynamics 365 Customer Engagement (D365 CE).
1. Sign into your D365 CE system.
2. On the Sales menu, click the drop-down menu to show the navigation menu flyout, and then under the Settings flyout, click OData Dialogs in the Lasernet list.
The Active Lasernet OData Dialogs page is displayed. Follow the steps listed below to create a new OData Dialog record.
3. On the Active Lasernet OData Dialogs page, click the NEW button.
4. Fill in all the required fields and then click the Save icon.
.../api/services/LACCRMServiceGroup/LACCRMReportExecuteService/newReport
Here is an example of this fixed part for the OData Submit Endpoint text box value:
.../api/services/LACCRMServiceGroup/LACCRMReportExecuteService/executeReport
As a result, a new OData Dialog record is listed on the Active Lasernet OData Dialogs page.
5. In the Active Lasernet OData Dialogs list, click the OData Dialog record you have just added. You can see the OData Dialog page opens for editing.
6. In the Lasernet Groups/OData Dialogs (OData Dialog) section, click a plus icon to add a group/OData Dialog record.
7. In the dialog displayed, enter a name in the corresponding text box as well as select a group and then click the Save icon to save changes.
In addition, you can add a new OData Dialog record when adding a new group or editing the existing one. To this end, see step 11 in the Configuration | Lasernet Connector for Dynamics 365 CE | Add a new button to a new flyout article.
ODATA Dialog fields
The following table defines some of the fields when creating a new ODATA Dialog record:
ODATA Dialog field query | Answer |
---|---|
What does Pre-Fetch Print dialog No/yes do? |
This is when the information needed to populate the printing dialog is fetched from FO ahead of time and stored in the browser's local storage (cache) when a form is opened. |
What does Fetch print Dialog On Click No/yes do? |
Same as above, except that it happens when the user clicks on the OData dialog button. Does not have a negative impact on performance, as it is only invoked when the user clicks on the button. However, the time saved using this will only be in the range of 50-400 ms. |
What does Wait for Fetch No/yes do? |
If the printing dialog should wait for any running pre-fetches (the two above), or if it should start its own fetch as soon as it opens. It's faster to wait for an existing pre-fetch than to start a new fetch, however, a pre-fetch will not be able to display an error message from FO. Any failed pre-fetch will require a fresh fetch and will result in extra time. |
What does Wait for Fetch timeout No/yes do? |
How many seconds the printing dialog should wait for a running pre-fetch to finish (option above), before starting its own fetch. |
What does Storage Timeout No/yes do? |
How many seconds the information for the printing dialog should be stored in the browser's local storage (cache) before being removed (expired). |
How to use the Image 16 field? How do you add a picture? |
Image 16 is an image with 16x16 pixels, 32 is 32x32 pixels, and ModernImage is for SVG (Vector) images.
Uses the following LAC web resources: Which are applied using Image16, Image32 and ModernImage:
|
Add a comment
Please log in or register to submit a comment.