Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Detect Embedded Grid Errors after Submitting from Parent Dialog

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • aburningflame
    replied
    Re: Detect Embedded Grid Errors after Submitting from Parent Dialog

    Hi Sarah, thanks for the suggestions. The issue is that there are actually 5 embedded grids - so i cant have the child grid submit the parent dialog.

    The example would work with 1 parent dialog and 1 embedded grid - but I really need the parent dialog to check for errors in each grid before submitting itself.
    For now - I have modified the Dialog Submit function to check {dialog.EmbeddedGrid_SVKEYWORDS}._isDirty property of every grid and only submit the dialog if all child grids have been saved.

    Unfortunate that the grid doesnt expose a haserrors method / member.

    Thanks for your input - appreciate it :) (Enjoy your day)

    Leave a comment:


  • TheSmitchell
    replied
    Re: Detect Embedded Grid Errors after Submitting from Parent Dialog

    Originally posted by aburningflame View Post
    Thanks for your reply Sarah. Doesn't look like a "hasErrors" is exposed.
    You would have to execute your dialog call inside your embedded grid because the hasErrors is only given to the event(s) that are triggered in the grid. There's the other issue that ajaxCallbacks are executed asynchronously. So, your IF check would executed immediately after calling submit on your embedded grid, even if the submit is not complete.

    You could solve this problem by putting the dialog submit code inside your embedded grid's after submit event:

    Code:
    if ( e.hasErrors == false) {
        var po = {grid.object}.getParentObject();
        if ( typeof (po) != 'undefined') {
            po.submit();
        }
    }
    You could take this a step further and define a function on the parent dialog in the javascript code section:

    Code:
    {dialog.object}.submitIfNoErrors = function (hasErrors)
    {
        if (hasErrors == false) {
            {dialog.object}.submit();
        }
    };
    ...and test for that function in the embedded grid...

    Code:
    var po = {grid.object}.getParentObject();
    if (typeof (po) != 'undefined') {
        if (typeof (po.submitIfNoErrors) != 'undefined') {
            po.submitIfNoErrors(e.hasErrors);
        }
    }
    Now you can include the grid wherever and not worry about the grid calling submit() in situations where it shouldn't.
    ---
    Sarah
    Last edited by TheSmitchell; 05-21-2014, 12:57 PM. Reason: forgot function keyword

    Leave a comment:


  • aburningflame
    replied
    Re: Detect Embedded Grid Errors after Submitting from Parent Dialog

    Thanks for your reply Sarah. Doesn't look like a "hasErrors" is exposed unfortunately.

    Leave a comment:


  • TheSmitchell
    replied
    Re: Detect Embedded Grid Errors after Submitting from Parent Dialog

    The grid object and dialog object are documented on the wiki: http://wiki.alphasoftware.com/~alphafiv/Grid+Component & http://wiki.alphasoftware.com/~alpha...alog+Component

    Leave a comment:


  • aburningflame
    replied
    Re: Detect Embedded Grid Errors after Submitting from Parent Dialog

    Does anyone know of any formal grid / dialog javascript documentation that is more thorough than the in-app methods / placeholder listings?

    Leave a comment:


  • Detect Embedded Grid Errors after Submitting from Parent Dialog

    I have the following code in a dialog which has embedded grids.

    Code:
    {dialog.EmbeddedGrid_SVKEYWORDS}.submitGridPart();
    {dialog.object}.submit()
    However, I want to detect grid errors and not submit the dialog if that is the case.

    Something like:
    Code:
    {dialog.EmbeddedGrid_SVKEYWORDS}.submitGridPart();
    if (!{dialog.EmbeddedGrid_SVKEYWORDS}.hasErrors){
       {dialog.object}.submit()
    }
    however, I am not sure where I can access has Errors or if this is even exposed / exists.

    It is available from the grids afterGridSubmit event.

    Any ideas? :) Would appreciate the help.

    Thank you in advance.
Working...
X