Model-driven app configuration entity – the most unusual approach I’ve ever seen, but it works

I was looking at the Omnichannel lately, and , then, I realized something that might be worth sharing.

You know how we would often create a configuration entity in our model-driven apps? Omnichannel is doing just that, but it’s taking it one step further. It provides multiple forms for the configuration entity so that each of the forms is exposing a subset of configuration settings, and, then, it adds links to the configuration record… for a specific form… to the left-hand navigation.

I mapped some of those on the screenshot below:

But, in general, there is just a bunch of forms:

Somehow, I never thought of doing it this way, but it actually does make sense – what we end up with is a very smooth user experience.

So, in case you wanted to do the same in your applications, here is how it’s done in the Omnichannel app:

You just need to use a url that would have all the right parameters, so here is an example FYI:

/main.aspx?appName=msdyn_OCAPP&pagetype=entityrecord&etn=msdyn_omnichannelconfiguration&id=d4d91600-6f21-467b-81fe-6757a2791fa1&extraqs=formid=a9587ef2-7470-4692-8db3-4c1bbe73a2a5