Showing results for 
Search instead for 
Did you mean: 

Javascript requires publish and should not


When designing a form at present if java script is to be used it must be published in the web resources section PRIOR to the form being tested. This presents problems as common java script files may be in use in previous form versions and are no longer relevant when a change is applied. As a result each new version of a form to be developed will require a separate javascript file and hence defeat the common repository intention of 2011. A better approach would be to, when a form is tested, read from the unpublished javascript repository. Basically the publish of the form and of the javascript should be tied together.

Status: Under Review
Level: Powered On
Status changed to: Under Review
Level: Powered On
Howdy Matt, I've added your suggestion for our list of considerations for the next version of CRM. Thanks for taking the time to send us your suggestions. Your input is very much valued! Shamiq Islam Dynamics CRM Program Manager This posting is provided "AS IS" with no warranties, and confers no rights.
Level: Powered On
Also, its a productivity killer for javascript developers to Browse, Save, Wait then Publish - I cannot think of a single scenario where I would not want to publish it immediately. Suggest we either take away the need to Publish, or add a Save and Publish button - should be easy to do and improve the lives of many consultants!!