Help for new Template for Dynamics 365 unified interface

[François (tebu-bio)]

Hello !

After reading this : https://www.3cx.com/community/threa...fed-interface-rather-than-classic-view.71395/
I tried to modify the default template. I think I found the right settings, the test function returns the right URL for the contact (if I copy paste it in my browser, it opens the right interface), but when I try by calling my number, it's still opening the default URL. It feels like it's still using the default template, and not mine. Should I do anything after changing the template? Thanks in advance !

 

[diamond9]

Restart the app on the computer and log out webclient, when you log back in it should reprovision and start using the correct template

 

[edossantos]

This is because you still have the contacts with the old URL in 3CX Contacts. Go to the 3CX Console > Advanced > Contacts > Delete CRM Contacts. This will delete the contacts from 3CX Contacts of type "CRM". Your Dynamics contacts are not affected.

 

[François (tebu-bio)]

Indeed, now it's working perfectly !

I didn't think about the contacts.
I have created a custom template, and it's working fine. I'm just adding a new parameter, "CRM App", and I fill it with the Unified Interface application ID. Then I add the parameter "appid=" in all the Output URLs . If it's not filled, it seems to go back to the standard web interface.

So it's something that could maybe be used in the standard template for Dynamics 365 with a bit more tests.

 

[edossantos]

Indeed, now it's working perfectly !

I didn't think about the contacts.
I have created a custom template, and it's working fine. I'm just adding a new parameter, "CRM App", and I fill it with the Unified Interface application ID. Then I add the parameter "appid=" in all the Output URLs . If it's not filled, it seems to go back to the standard web interface.

So it's something that could maybe be used in the standard template for Dynamics 365 with a bit more tests.

Thanks for your feedback, and glad to know that you managed to get this working. We will probably implement this as well in the standard template, however we can't provide any ETA for this.