Extra postback in Nevron web part?


Author
Message
Dan Jordan
Dan Jordan
Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)
Group: Forum Members
Posts: 4, Visits: 2
I have a web part page that includes a Nevron Chart for SharePoint web part. I use a custom-developed web part that provides parameters to the Nevron web part using JavaScript, since this option seems to perform better than using connected web parts.

The page is functional but it's slow. When I look at the calls going back and forth to the server via Fiddler, I see the following:

POST /_layouts/Nevron/Chart/NChartCommander.aspx HTTP/1.1 (initial call; parameter not set yet)

POST /_layouts/Nevron/Params/NParamsCommander.aspx HTTP/1.1 (set parameters here)

POST /_layouts/Nevron/Chart/NChartCommander.aspx HTTP/1.1 (final call to web part with parameters)

It appears that the text of the request in the first and second calls to NChartCommander.aspx is identical.

Is there a way to dispense with the first call to NChartCommander.aspx, since the parameters aren't known at that point and won't be until I set them with JavaScript after the page loads?

Thanks in advance,
Dan Jordan
Reply
Nevron Support
Nevron Support
Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)
Group: Administrators
Posts: 3.1K, Visits: 4.2K
Hi Jordan,

Yes - using custom parameters with Nevron JScipt are usually performing better than connected webparts, since the latter perform a complete postback to force the page to go through the web parts connection phase (page pre-render).

The client side will initiate a InitXXXParam POST request, after a certain delay, any time you call the respective NInitXXXParam method. The delay is needed for a multiple params on the page to be grouped in a single Init Request to the server, so the initial POST that you get is perhaps from a global script block, that gets executed when you load the page.

Can you please elaborate on the client side scipt that you use to Init/Set Nevron parameters and to respectively refresh the Nevron webparts. Please note that Nevron parameters are by default initialized to REFRESH ALL Nevron WebParts when any paramter changes. However you can init parameters do not refresh the webparts - to force a refresh of the webparts that use this parameters you can call the NRefreshWebPart method.

See this topic in the help:
Building Dashboards > Parameters in SharePoint Pages > Custom Parameters with Nevron JavaScript API

Best Regards,
Nevron Support Team


GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search