Breaking news from around the world
Get the Bing + MSN extension
Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
Thanks in advance to those reading the post!
I would like to open up a discussion and see what everyone thinks about the questions below.. I have a few forms that have a lot going on during the onload event and I am currently being asked to add more to that so i find myself debating more creative solutions to "spread the processing burden" around and improve performance. My questions to start would be:
1) Is there anything you would never do onload?
2) Best ways to measure the impact of your changes.
3) Would you ever set a timeout to defer processing and "spread the burden out?"
4) Am i grossly underestimating the speed of .js? I know this answer is dependent on what i am doing specifically. For example, if i am making an API call there are other factors to consider obviously.
Thanks again to anyone who replies. My client-side scripting experience in D365 is limited to a year'ish and i'm still learning a lot but I am loving it so far. Just want to make sure i am considering everything.
Things to consider:
There are always creative ways to do things, Just be careful. How many calls do you have at the moment?
I think it all comes down to performance and business need. If you are adding a lot of JS and this causes your page load times to be unreasonable for the business, it might be the wrong place for them.
Like you said it is hard to determine without knowing the exact business needs, but a system needs to perform adequately for the business users.
You can call many things when the form loads, but you should determine whether everything has to be loaded synchronously. Anything that can be deferred probably should.
See the following link and see if anything there helps you:
Hope this helps.
Business Applications communities