I have an external web application that displays D365 data (fed via export to data lake) which includes reports like AR Aging or GL details. While reviewing the reports, my users would like to drill into the original document in D365 from the external web application. Is Deep Links a good use case for this or is there a better approach to navigate to a D365 form and specific record from an external application? While investigating deep links, it seems like I may have to create a D365 endpoint that would generate the link for the external application using the arguments like which menu item and which record they would like to open. Is there a better option? I noticed some of the inquiry forms that we'd like to drill into (like Voucher Transactions inquiry in General Ledger) didn't have a clear way to drill into a specific record. It's almost like I'd need to provide the query for the inquiry as well as the query to drill down to the specific row. Any suggestion on how to better implement a drill into the source record from an external application would be greatly appreciated!
The deep links are a standard feature. You can check out how they are created and call the same logic. In case you have a lot of records, creating all the links, record by record, will consume some performance. You can also consider exporting simple details, like a record ID. Then create a webservice that can be called using the record ID if a user wants to drilldown. At that point in time the deeplink will be generated and you can redirect to the URL. In this last option, the application will not create thousands of deeplinks, but only one at the time required.
Using Deep Links is indeed a common and effective approach to navigate to a specific form and record. Deep linking allows you to construct URLs that, when opened, take the user directly to a specified form and record. Here are the general steps you might follow:
Construct Deep Links:
Identify the form and record you want to link to in F&O.
Construct a URL that includes parameters such as the form name, record ID, and any other relevant information.
Dynamics 365 Endpoint:
You may need to create a custom endpoint that can generate these deep links. This endpoint could take parameters like the form name and record ID and construct the appropriate URL.
Security Considerations:
Ensure that the user accessing the link has the necessary permissions in Dynamics 365 to view the specified form and record.
Best regards,
Kevin
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.