Views that exceed a preset level of complexity are rendered by the server automatically instead of in the web browser.
http://localhost/views/Supplies/MyView?:render=trueor
http://localhost/views/Supplies/MyView?:embed=yes&:render=true
Option 2 Redesign views and dashboards with reduced complexity, such that server-side rendering does not occur for the mark data. Complexity factors include number of marks, headers, reference lines, and annotations.
Option 3 (Tableau Server) Increase the rendering complexity threshold using "tsm configuration set vizqlserver.browser.render_threshold". See tsm configuration set Options for more information.
Attempting to force client-side rendering using the URL parameter will not change this behavior in all cases. This is because the the server automatically renders the view using "server-side" rendering when it determines that the view is complex and performance would improve by forcing server-side rendering. This involves generating an image of the view on the server so the amount of data sent to the client is limited. When a view is "client-rendered," we have all the mark data on the client, so we can respond immediately to interactions (such as showing borders and changing to the mouse icon on hover). When the view is rendered on the server we don't have item-level detail about the marks, so we don't show the borders or mouse icon changing on hover.
Note: If a view uses the polygon mark type or the page history feature, server-side rendering is always performed, even if client-side rendering is enabled.
001473251

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.