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

Using page variables in an xbasic callback in a UX

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

    Using page variables in an xbasic callback in a UX

    I have a UX component that makes an xbasic callback. A page variable is used as an argument. I can display the page variable on the a5w page where the UX component is, and in a field on the UX by making the default value = pageVariable.department. However, after many attempts, I cannot get request.variables to read the variable in the xbasic script Am I missing something basic?
    Here is the code to get the variable:
    Code:
    dim Request.Variables.department as c
    if variable_exists("Request.Variables.department")then
    	department=alltrim(Request.Variables.department)
    end if
    I have also tried different variations, like
    Code:
    dim department as c
    if variable_exists("Request.Variables.department")then
    	department=alltrim(Request.Variables.department)
    end if
    The page variable is not retrieved; the value of department is blank, even though the page variable is there.

    I also tried to set an argument in the UX to get its value from the page variable, but I could not figure out how to use that argument in my script, either. What would be the right way to refer to this value in an xbasic call back?
    Last edited by richardurban; 12-25-2014, 01:06 AM.
    Richard Urban

    Grocery Delivery Software for Stores and Entrepreneurs: http://www.urbangrocery.com

    #2
    Re: Using page variables in an xbasic callback in a UX

    Not sure if this is the best way of handling it but this should work...

    You said you can make a field equal to the page value. If that's correct then you can use that field as an argument in xbasic. Lets say the field name is "test". Here is how you can use "test" as an argument...

    Code:
    function MyFunctionName as c (e as p)
    
    dim cn as sql::connection
    dim args as sql::arguments
    dim rs as sql::ResultSet
    
    args.set("arg1",e._currentRowDataNew.Test)
    
    cn.Open("::Name::sql")
    
    sqlSelect = "SELECT Field1 FROM MyTableName WHERE Field2 = :arg1"
    
    cn.Execute(sqlSelect,args)
    
    cn.FreeResult()
    cn.close()
    
    end fucntion
    The code above is just an example of course...it doesn't check for errors or do anything with the data.
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Programmatic-Technologies.com
    Independent Developer & Consultant​​

    Comment


      #3
      Re: Using page variables in an xbasic callback in a UX

      Originally posted by richardurban View Post
      I have a UX component that makes an xbasic callback. A page variable is used as an argument. I can display the page variable on the a5w page where the UX component is, and in a field on the UX by making the default value = pageVariable.department. However, after many attempts, I cannot get request.variables to read the variable in the xbasic script Am I missing something basic?
      Kind of...

      Request (page) variables set in an a5w page are not available in XBasic Ajax Callbacks.

      They are available in the Server-side onDialogInitialize event. In this event you'd get the Request var and assign it to a State variable. Then that State variable will persist through your code and be available in callbacks.

      From your a5w page you have something like this...

      Code:
      http://phantom:81/AlphaTest/ux_Request_Var_Callback.a5w?id=123
      Which gives you a Request variable with the name of "Id" and a value of 123.

      In your UX onDialogInitialize event you would do something like this...

      Code:
      if variable_exists("request.variables.Id") then
      	e._state.myPageVar = request.variables.Id
      else
      	e._state.myPageVar = "Sorry... No Page Var"
      end if
      And then... in your Callback...

      Code:
      function getPageVar as c (e as p)
      
      dim myPageVar as c = e._state.myPageVar
      
      getPageVar = "alert('my page var is " + myPageVar + "');"
      
      end function

      Comment

      Working...
      X