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

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

How to use 'Logged in UserID' in a 'Before Update Trigger (MSSQL)'

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

    How to use 'Logged in UserID' in a 'Before Update Trigger (MSSQL)'

    Help

    Is there a way to use the Mobile/Browser "Logged in UserID" and pass it to the "Before Update Trigger (MSSQL)" for use in CreatedBy/UpdatedBy fields in the Table?

    If so how would you do it?

    MarkMoss

    #2
    Re: How to use 'Logged in UserID' in a 'Before Update Trigger (MSSQL)'

    Welcome to AAForum, A new user answering this but hope will chime with the overall flow but other Alphaholics will confirm if niftier ways are possible.
    First things first, we have to capture the logged in user. In my case, I use a tabbed UI implementation and the "form" that updates/inserts this record will have this code in the onDialogInitialize

    Code:
    dim lUser as c
    lUser = a5ws_getcurrentuser()
    Could also use Session.lUser = a5ws_getcurrentuser()

    In server-side onAfterDialogValidate, we set-up the action Scripting that performs a save submitted data to table. It is within this function that we will define an additional operation to perform an update of the currently saved data to fill in the User name and any other data required.
    Once the script tag has been added, you will need to go in edit it. Within this window, we can add more functionality. See bottom of the dialog,

    http://screencast.com/t/NZWCeGYgN

    Here I have added code for afterRecordInsert. See the helper note on what that function does. Create the xbasic for this. Please see the code I use in my case.

    Code:
    function afterRecordInsert as v (e as p)
    	'debug(1)
    	dim cn as sql::Connection
    	dim sqlStmt as c
    	dim flag as l
    	dim js as c	
    	flag = cn.open(e.connection.ConnectionString)
    	if flag = .f. then
    		js = "alert('Could not connect to database. Please contact support team.');"
    	else
    		js = "alert('Connected to database ok');"
    	end if	
    	sqlStmt = "update customer set CreatedBy = :vUser, CreateDate = Now() where id_Customer = :priKey" 
    		
    	dim args as sql::Arguments
    	args.Add("vUser", Session.lUser)
    	args.Add("priKey", e.primaryKeyOfInsertedRecord )
    		
    	flag = cn.Execute(sqlStmt,args)
    	
    	if flag = .f. then
    		dim js as c
    		js = "alert('Could not execute query. Error: " + js_escape(cn.CallResult.text) + "');"
    		cn.Close()
    	else
    		js = "alert('Connection and SQL execution ok');"
    	end if
    end function
    In the code, I am making use of the user identifier within the args.add. Also the key of the current record is now available in this function as per notes.
    Hope this helps
    Regards,

    Kotin Karwak
    Developer Edition
    Version 12.3 Build 2684
    System Addins: Build 4438
    Build machine Windows Vista
    Skype: mateso08

    Comment


      #3
      Re: How to use 'Logged in UserID' in a 'Before Update Trigger (MSSQL)'

      Not sure this is exactly what you are looking for, but if all you are trying to do is capture the the current user to notate who updated/created the record, for created, just put =a5ws_getcurrentuser() as the default value of a textbox bound to the the CreatedBy field (I use this in all new record dialogs). For updated (which I have never used in my projects), either make the textbox a calculated field with the expression =a5ws_getcurrentuser() if that does not work(never tried it), you can always create a session variable as shown by Kotin and set the calculated expression to SESSION.USER. Note: you should use the Session.User format to set the variable and be sure to publish it to the client-side in properties.

      Comment


        #4
        Re: How to use 'Logged in UserID' in a 'Before Update Trigger (MSSQL)'

        Ecalan, Does work!
        Regards,

        Kotin Karwak
        Developer Edition
        Version 12.3 Build 2684
        System Addins: Build 4438
        Build machine Windows Vista
        Skype: mateso08

        Comment


          #5
          Re: How to use 'Logged in UserID' in a 'Before Update Trigger (MSSQL)'

          If data is not bounded to the UX component.

          Validating Data Before it Saved (I also used it for updating)
          When you use this action, all data validation settings that you define for controls on the UX are enforced before the data is saved. However, you might want an additional level of validation. You can use the:
          1) before Update SQL computed
          2) before Insert SQL computed
          server side events for this purpose.
          Another common use of these events is to modify submitted data before it is committed.
          For example, assume that the table you are editing has a field called 'timeLastUpdated' and you want to automatically store the current date/time in this field, you could put this code in your event handler

          e.dataSubmitted.timeLastUpdate = "" + now()

          These two event also allow you to set the:
          e.abort flag. If this flag is set to .t., then the insert or update is not performed.

          More here: http://news.alphasoftware.com/V12Pre...seNotesV12.htm

          Regards!

          Comment

          Working...
          X