Have a page that contains numerous models, and a range of components linked to these models spread down the page. Components for a specific model are dispersed through the page, not all grouped together.
Problem is, on a save error I get standard messages replicated up the page against each of the multiple components linked to the affected model. Looks horrific. Thus, Im trying to intercept all errors and aggregate them against one component at top of page.
in my save snippet, I am trying to push each error to target UI component using initiatorId param but getting nowhere. Any suggestions on how this is used? Relevant sections of my code below:
var myPage = skuid.$('#FormTitle');<br>var myeditor = myPage.data('object').editor;<br>.<br>.<br>.<br>models.save({ callback : checkResult }); // assume I save the models<br>function checkResult(result){<br>if(!result.totalsuccess) {<br> myeditor.handleMessages(result.messages,{ initiatorId : "FormTitle" } );<br> return false;<br>}
If you can’t figure out the solution you are pursuing, you could instead create separate models for each component. It isn’t the cleanest or most convenient option, but it may save you a few hours of trying to figure out how to do what you are trying to do.
Thanks Raymond. I appreciate your response. Unfortunately with 11 models already that’d expand DML queries out to say 30 for the page, affecting efficiency and performance significantly. There must be a simple way to define where to put error messages surely ?
On certain components (like field editors) in the component settings there is a “Display” tab. On the display tab, there is an errors tab. It allows you to determine if errors are shown inline and whether you only want them to show upon hover.
Yep good suggestion. I did try that and so now errors appear on fields AND against all elements in the page that is bound to the model that has validation errors - nasty UI experience! I keep hoping that there is a way to consolidate all errors from all models onto one page element. Seems page hacks are the next step which seems counter productive.
