Share
Report
2,175Hi all,
So I've been testing the new Wave 1 release for 2020 in my dev environment as I've got several javascript scripts that load when the email form loads. So I wanted to make sure the contextual email pop-up that appears in context of for example a case still calls the functions I've set on load of the email. So this all works well with the original Enhanced Email form. I then tried to save another copy of the Enhanced email.
We'll call this form Enhanced Email - Test. I set the form to be visible by everyone as there isn't a specific security requirement to hiding the form.
Even though there isn't a specific security role assigned to this form, I have custom Model-Driven apps for different teams within my company, which means I still want to ensure that if someone is using Dynamics in a specific model driven app I want only the Enhanced Email - Test to be visible and usable in that app. So I then opened the app editor and in the forms for the email ensured that only the copied Enhanced Email - Test was available for the specific app.
This worked when we were only working with main forms of the interactive experience types but when I publish the app and attempt to create a email, the contextual email defaults back to the original Enhanced Email form as you can see below.
You can also see that I can also select all the other email forms which I have not ticked for this specific model -driven app. It's really strange. I mean I could probably create different security roles and run the restrictions through that method but what's the point of the model-driven app builder's ability to allow you to pick and choose the forms if it doesn't work with the new enhanced emails.
All responses (
Answers (
