creating multiple java script web resources for single entity form

(0) Share

Report

Posted on by Yashpal Rajput

Hi,

I have created multiple multiple java script web resource libraries in solution and added libraries on single form.I want to ensure whether is it good practice to create multiple web resources ? How this will impact on performance ?

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (3)

Verified answer

Aiden Kaskela 19,696 on at

Like (1)

Report

Hi,

I think it's a balancing act between performance and maintainability. You don't want to load more than you need because it'll be wasteful, but you don't want to be overly-focused on performance to the point where you can't maintain your code.

As a general rule, smaller files load faster than big ones, and the less files there are, the faster it can load.

If you have a lot of javascript for specific entities, I would break up the web resources by entity so you're loading only what you need to, all at once. If your js is more general, like standard date manipulation, you should keep them in separate files in case you need to change the functionality, then there's only one place to do it.

With that said, unless you're loading huge js libraries, I haven't seen much of an impact on how the js functionality is grouped.

I hope this was a help Yeahpal, if so I would appreciate if you would mark this as the verified answer.

Thanks!

Aiden

Was this reply helpful? Yes No
Verified answer

Aileen Gusni 44,524 on at

Like (0)

Report

Yashpal,

I also actually implement the same thing to make our function is modular and somehow needs to download global or common function that stored in single global javascript that must be accessed by other entities.

So far not really affected the performance, this is for better maintenance.

Thanks.

Was this reply helpful? Yes No
Aiden Kaskela 19,696 on at

Like (0)

Report

Hi Yashpal,

If you're running CRM 2015, javascript files are loaded in parallel, so if your js files can be loaded in any order (i.e., the don't reference each other), having them broken up won't hurt nearly as much as previous versions. It might actually be faster, but I can't find any details on that.

Here's some more details on form load updates:

blogs.technet.com/.../form-load-time-drastically-reduced-with-the-new-form-rendering-engine.aspx

Thanks,

Aiden

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

Hi Yashpal,

I would say is :

1. You can have one JavaScript Webresources Entity wise(Eg account.js, contact.js, opportunity.js). This will help you to bifurcate the JS web-resources Entity.

2. You can create one "CommonWebresource" file and include all common function which are required to be used frequently. This will remove redundancy of functions in different web-resources.

It will be good if you keep one JS web-resource i.e. specific for that entity and one Common function JS web-resource on Entity form.

Thing need to be taken care in parallel i.e. maintenance and performance, The less code less time to load , less files less time.

I have gone through various article/bogs but didn't find any thumb rule for this. Hope This helps !!

Regards,
Kamran

Was this reply helpful? Yes No