Timeline for Dymamic components execution order issue
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 17, 2013 at 17:25 | comment | added | Vlad | Exactly. That how we have fixed this. I consider this as a temporary workaround and home SF will fix this soon. | |
| Apr 17, 2013 at 16:37 | comment | added | crmprogdev | So in-essence, it sounds like the issue is that it needs to either "re-render" after the assignment takes place or somehow refresh itself, preferably before the html is ever sent to the viewstate/browser upon initialization? Would that summarize it? | |
| Apr 17, 2013 at 16:22 | comment | added | Greg Grinberg | The issue is that this doesn't appear to be following execution order in the docs. componentValue="{!headerComponent}" is being run before the assignto is evaluated. | |
| Apr 17, 2013 at 15:34 | history | answered | crmprogdev | CC BY-SA 3.0 |