🔴
Though they wish they didn't, CIOs often spend the majority of their IT budget on support.
I dream of a world where all this time and money is saved.
A place where applications just work, so there's
No tickets.
No complaints.
No business downtime.
To get there faster, I've started working in Microsoft's core, helping D365FO Specialists to build systems that automatically detect and solve problems.
🟡
One of my clients, Maria sent me this request earlier this month,
Can we jump from your app https://d365.mobeez.com/ directly into the D365FO record which has the fault?
PS: Like a failed Bank Rec or a stuck Purchase Order?
I called. "Maria, this is going to take a week's worth of work. Is it worth it for to save a few seconds of clicking?"
We went back and forth for a few minutes. Actually, it was more back and less forth but in the end, I could see that Maria was frustrated by having to drill down on dozens of faults, always starting at the home menu.
🟢
So, I researched Microsoft's D365FO Deeplink technology. It allows us to jump to the right form by crafting a URL, something like https://D365/Customer=xxxx
In the video below, Maria is browsing a Business Process for Bank Reconciliations.
An alert is sent for some bank statements that are not validating this morning.
Maria clicks on the link which takes her to the Bank Rec Dashboard in Mobeez.
She clicks on the number 55, when then lists the failed bank statements.
When she clicks on the D365 link column, a new D365 tab is opened, and the relevant bank statement is shown.
In this case, it's ok, so Maria approves the line and move onto the next bank statement.
I must say, what an absolute joy it is to use.
We no longer have to explain how to drill down into a specific form because the end-user is literally taken to the correct spot every time. And since it's a safe URL, they can share it, knowing that whoever clicks on it, will be validated by Microsoft's usual security checks.
If you're interested in having D365 Deeplinks in your application, I've listed my sources below and a few FAQs. Feel free to DM if you want more info.
Creswell Casey
FAQ's
Q1: Does this require code? Sadly yes. There's some X++ code and you need to find the relevant form names. There's also a nifty trick in the blog articles below which requires some additional code, if you're running the URL creation process from a batch.
Q2: Does the URL give away private information? Microsoft doesn't reveal any private information. It's similar to a normal D365FO URL. The xxxxxxx is a reference to your own D365 instance.
https://xxxxxxxxx/?cmp=PSUS&prt=PS&mi=display:BankAccountTableListPage&pageType=Details&q=BgAAAPVoxDGuaxp8erHga6aOM1CloKcG9WjEMa5rGnx6seBrpo4zUKWgpwZ%2bp8OjHjKNa3hfkSsbCONKytfH8YTgDBdxre1drSOQAoW4uiCyR2bFz36jv6al34OdmcA0TAsII%2bAUX9y%2fTJVRK2jDqwS0zqjBgiEHVShtExriYDhZ4j7GzCia37UleTY7oh7lKtPEbA4kmgxqRzd3a57Y%2bMEA05KVYNF8rso0FJygSspz7HioYmWVCew9uxIsGLxdMC87lyqYHhVE8LlJhAp69v%2fJwncfYdw2ix9DGGAUPbGa%2fXPR28ZTQow8RpkVihO1sP0QweLUjIwdppegUYKNeCLGnnQoyC13qMk25BH%2fJ3HBrF3r3u1jwQTFoNFNYx6iLh0DrXPANuSyIO5pZG5Yn1D8aU0Gez%2b%2fvSJvjW9wkR40CeNOsw1u9GKbphon80u1oza27NltsoWUuvmJK7sOBmo0Jjt0P9kbcZioJPAQJiKz9OeQzIF5m2BCc3Dl2zneFDT5FXSO%2fJlR4Plwce2a1y9CYqyMFu2LK%2fyHiQDd%2b56nZ04likn7L9i7wlvvGtC10gTlVhHs4AJ8i%2baWj5D57fvm%2bYVoGH2i900Efk%2blkICea3wMkwcbnFQhnvhPiaE5X5YuU%2f8VTIxVYq4PxEkKodXkU%2fi7yfI%2fmH9kwCeepH8zMkiCrPaK5DovhmyD8clN5scHJOOrbCv2W6I08zfK4LkiYZgK%2bzRSM9VJseBmnAzQQPQDlTzLWo99JYucEAFA%2bvDqdUqgewnayxNM5nXLNylIELaW6UjBvMZV61Rm5jbY9G%2fhauPboyKR8moZ3mOpP9kKAvVpEhDtwlbN1%2b0Z9K9FkfeG%2fhH9MJzsD81BEKBV43NUzaZRPJkTR%2fEqampZXHD0oLlBovwKIMmC
Q3: Can another user access this link to bypass security? When any person, anywhere in the world clicks on this link, then Microsoft will do all the usual security validation such as (domain login, multi-factor authentication if set, security groups, account enabled etc). If all good, then the user will gain access to the form and data.
Q4: How quick does the URL open? It's the same time as opening another D365 session. You can even embed the new instance into your own app by using modifiers in the URL.
Q5: How do you send the URL to the external application? Our X++ code runs as a batch and generates relevant URLs for records that we believe have an error. We use an API to send those URLs and other information to our external application. The external application then messages the relevant users and includes the URL.
Articles Researched
For a short introduction to the technology, I recommend Microsoft's documentation.
To learn more, please review these blogs. They helped me to quickly write the X++ code and build a solution.
Comments