Chart Conflicts not addressed by release 6.5

  • 1
  • Question
  • Updated 4 years ago
  • Answered
Archived and Closed

This conversation is no longer open for comments or replies and is no longer visible to community members. The community moderator provided the following reason for archiving: Ticket not helpful to others - problem resolved in release 6.6

Thanks for your teams amazing release and quick patch! Skuid has created a massive value for our org and has allowed me to move passed tedious administrative tasks and onto those cool projects developers are passionate about. :-)


So, I'm having the following conflict arising out of page includes and charts. The page include with charts renders perfectly when it is in the initial load page but not in subsequent page includes in other tabs. If I switch to those tabs and refresh the page (F5), the new tab's page include renders and the old tab's does not. Granted, I have a solid workaround - switch to the tab and refresh the page. 

I've tried the lazy load technique, and I believe I'm missing something. My page has a relatively complex tree of tabs and page includes. It seems like lazy load can be set in the following three places:

  • Tab set
  • Tab
  • Page Include

I've tried several different configurations of these lazy loads (All set, none set, page include set only), and I can't get the site to behave how I want it to.

What can I do to create a consistent experience?





(Did I mention SuperBank is freggin' awesome?)
Photo of Griffin Brown

Griffin Brown

  • 2,798 Points 2k badge 2x thumb
  • good

Posted 4 years ago

  • 1
Photo of Unmesh Sheth

Unmesh Sheth

  • 466 Points 250 badge 2x thumb
I also tried 6.5.. Page behavior is same as in 6.4.

1) I have a page with multiple tab.  
    For Tab 1 - I have a page include which has has a chart and table both.  This doesn't work. Yes. Lazy Cache is turned on.

   For Tab 2 - I have a page include with a chart and table... This page shows fine consistently.


2) For another page, I have ten tabs with each includes page include.  3 out 10 pages do not render.

Please let me know what am I missing?

Thanks,
Unmesh
Photo of J.

J., Official Rep

  • 7,746 Points 5k badge 2x thumb
Griffin,

Odd. I'm having trouble replicating the behavior in our dev org and our demo org (which is also running 6.5), so I must be missing something. Would you mind granting login access again so we can take a closer look? Thanks.
Photo of J.

J., Official Rep

  • 7,746 Points 5k badge 2x thumb
Actually, I think I just got this replicated. Let me describe the behavior, and let me know if it matches with what you are both experiencing:
  1. Scenario: you have a page with multiple tabs, more than one of which contains a page include with a chart in it.
  2. The first page include with a chart on it that you load works fine. It doesn't matter which tab, just that it's the first one that loads.
  3. If you click on another tab with a page include that contains a chart, it fails to load, and the console reports a javascript error.
  4. Refresh the page, and you're back at #2.
Photo of Unmesh Sheth

Unmesh Sheth

  • 466 Points 250 badge 2x thumb
Pretty much.

Perhaps you may want to compare javascript error that you saw and what I have been seeing. What's interesting that this pages seems to moving time to time.

https://www.dropbox.com/s/xfkvui3apnw96oa/Screenshot%202015-01-11%2013.36.40.png?dl=0
https://www.dropbox.com/s/iz1nydau3agqa5a/Screenshot%202015-01-11%2013.38.01.png?dl=0

Thanks,
Unmesh
Photo of Unmesh Sheth

Unmesh Sheth

  • 466 Points 250 badge 2x thumb
When will I be able to test this fix?
Photo of J.

J., Official Rep

  • 7,746 Points 5k badge 2x thumb
Our next release is targeted for Friday of this week. I expect the fix to be included in that package. I'll make a note to double-back to this thread when the fix is delivered, just so you have confirmation that it was included. Thanks!
Photo of Zach McElrath

Zach McElrath, Employee

  • 50,654 Points 50k badge 2x thumb
The next release, 6.6, should fix this issue, and it is now available on the Skuid Releases page.
(Edited)

This conversation is no longer open for comments or replies.