Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook
Devcon 2020 Goes Virtual! LEARN MORE >

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

Dialog2 � Is Setting Session Variable in OnDialogExecute Server-Side Events Possible?

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Dialog2 � Is Setting Session Variable in OnDialogExecute Server-Side Events Possible?

    I have a field in a Dialog2 component that gets the name of the current logged in User when the dialog is initially opened. I�m using the following code in the OnDialogInitialize Server-Side Events:

    e.control.User_ID = session.ulink

    When the dialog is submitted, the User ID is saved to the SQL table. However, once the User clicks the New Record button within the same Window/TabbedUI pane, the event won't fire since the dialog wasn't closed and reopened. I do not want my client to have to close and reopen the dialog for each new record they enter in order to capture the User ID.

    My question is - What event can I enter in the OnDialogExecute Server-Side to reset the field with the User�s ID again for the new record? I�ve tried entering the same code above, but the dialog doesn�t recognize it. I've been fiddling around with some of the other items in the default prototype examples, but I�m still too new to Alpha5 to have a good grasp of using arguments or JavaScript, and haven't had any success. I did manage to find a work-around using "e.control.User_ID = session.ulink" in the DialogValidate event, but it requires another button on the dialog page that the User has to click to Validate the new record before submitting. While it's not the end of the world, it's inelegant to say the least and requires two extra button-clicks to get it to work properly - essentially the same amount of clicks to close and then reopen the dialog, which I'd like to avoid.

    With the Grid component, this process was explained in some videos with the AfterInsertRecord and AfterUpdateRecord functions. Has anyone run into anything similar that works for the Dialog2 component, or is there something I'm overlooking? If so, I�d sincerely appreciate a point in the right direction.

    Regards,
    Melissa
    Melissa Smith
    Triskelion Consulting, LLC
    Tags: None
    #2
    Re: Dialog2 � Is Setting Session Variable in OnDialogExecute Server-Side Events Possi

    Originally posted by Melissa Smith View Post
    I have a field in a Dialog2 component that gets the name of the current logged in User when the dialog is initially opened. I�m using the following code in the OnDialogInitialize Server-Side Events:

    e.control.User_ID = session.ulink

    When the dialog is submitted, the User ID is saved to the SQL table. However, once the User clicks the New Record button within the same Window/TabbedUI pane, the event won't fire since the dialog wasn't closed and reopened. I do not want my client to have to close and reopen the dialog for each new record they enter in order to capture the User ID.

    My question is - What event can I enter in the OnDialogExecute Server-Side to reset the field with the User�s ID again for the new record? I�ve tried entering the same code above, but the dialog doesn�t recognize it. I've been fiddling around with some of the other items in the default prototype examples, but I�m still too new to Alpha5 to have a good grasp of using arguments or JavaScript, and haven't had any success. I did manage to find a work-around using "e.control.User_ID = session.ulink" in the DialogValidate event, but it requires another button on the dialog page that the User has to click to Validate the new record before submitting. While it's not the end of the world, it's inelegant to say the least and requires two extra button-clicks to get it to work properly - essentially the same amount of clicks to close and then reopen the dialog, which I'd like to avoid.

    With the Grid component, this process was explained in some videos with the AfterInsertRecord and AfterUpdateRecord functions. Has anyone run into anything similar that works for the Dialog2 component, or is there something I'm overlooking? If so, I�d sincerely appreciate a point in the right direction.

    Regards,
    Melissa
    Hi Melissa,

    I think
    Code:
    e.control.User_ID = a5ws_getcurrentuser()
    in the OnDialogExecute event will do what you're trying to do.
    Gregg
    https://paiza.io is a great site to test and share sql code

    Comment

      #3
      Re: Dialog2 � Is Setting Session Variable in OnDialogExecute Server-Side Events Possi

      Gregg,

      Nope; didn't like that either.

      It's almost as if the OnDialogExecute event is missing some features; the other events have quite a few options in the default messages to work with. Thanks for the suggestion though!
      Melissa Smith
      Triskelion Consulting, LLC

      Comment

        #4
        Re: Dialog2 � Is Setting Session Variable in OnDialogExecute Server-Side Events Possi

        So, I may have figured this out..., although I need to run a few more tests to make sure it wasn't a fluke.

        I entered the following into the DialogValidate and the AfterDialogValidate events:

        e._set.user_id.value = session.ulink

        I made sure to place it before the aftervalidate event: ExecuteServerSideAction("Save Data::Submit")
        Melissa Smith
        Triskelion Consulting, LLC

        Comment

          #5
          Re: Dialog2 � Is Setting Session Variable in OnDialogExecute Server-Side Events Possi

          Posting an update to my testing. I have three Server-side Events to accomplish capturing the session variable:
          function onDialogInitialize as v (e as p)
          e.control.USER_ID = session.ulink
          end function

          function dialogValidate as p (e as p)
          e._set.USER_ID.value = session.ulink
          end function

          function afterDialogValidate as v (e as p)
          e.dataSubmitted.USER_ID = session.ulink
          e.dirtyColumns = e.dirtyColumns + crlf()+ "USER_ID"
          ExecuteServerSideAction("Save Data::Submit")
          end function


          I don't know if this is overkill, but it is working and for now that's all that matters. If anyone has a more elegant solution, I'm all ears (or I suppose eyes).
          Melissa Smith
          Triskelion Consulting, LLC

          Comment

            #6
            Re: Dialog2 � Is Setting Session Variable in OnDialogExecute Server-Side Events Possi

            Couldn't you just set the default value for the control, in the Properties->Field Properties->Default value to this?
            Code:
            =session.ulink
            Jim Coltz
            Alpha Custom Database Solutions, LLC
            A5CustomSolutions.com
            [email protected]

            Comment

              #7
              Re: Dialog2 � Is Setting Session Variable in OnDialogExecute Server-Side Events Possi

              Jim,

              I did initially have the field properties set with the session variable like you suggest. It stops working, though, once a record is saved and then a new record is started within the same window or TabbedUI pane. The default property/session variable works like a charm in a Grid component (using the server side events), and will work on subsequent "new records" without closing a pane or window. But, I haven't been able to get the event to fire again using the default field properties within a Dialog2 component without completely closing and reopening the Dialog2. Hence, my really ugly work-around.

              It's quite possible that I'm missing some key element to get it to work the way I expect it to...
              Melissa Smith
              Triskelion Consulting, LLC

              Comment

              Previous template Next
              Working...
              X