It will restrict deletion of field(s) if it is being consumed in a js web resource. In earlier versions user was able to delete field(s) even if it is used in a js logic, and it causes exception in js execution.
- Dependent field(s) value will be available on form UI, even if it is not added on form. That’s right you don’t have to fetch its value from CRM now (earlier we have to fetch field(s) value using odata or web API if it is not available on form and its value is needed in js logic.)
js web resources will be shown in field dependencies.
To add attribute dependencies, follow below steps
- Open a web resource (from a solution, this option is not visible if you open…
View original post 52 more words