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

From Xbasic Function to component

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

    From Xbasic Function to component

    I am uploading a document using the standard xbasic function. The function works well however I need to store the path and doc name created within the function in a field called completeFileName to a component called doc_loc. I am a new user and do not know (and cannot find) the code to let doc_loc = completeFileName from within the function. It must be dead simple for all you old hands.

    #2
    Re: From Xbasic Function to component

    In the File Upload action there should be an option called "On Stored filename compute Xbasic function". You can create an xbasic function to name it whatever you want and put it wherever you want.

    The Xbasic for something like this looks similar to this:
    Code:
    function FileName as v (e as p)
    'This function is called to compute the filename for the uploaded file.
    'The e object that is passed in contains:
    
    'e.targetFileName = the filename for the uploaded file. This is computed based on the setting for the upload folder and the name of the file on the client machine
    'e.imageBinaryData = binary data that was uploaded
    
    
    'In addition, the e object contains
    'e.tmpl  - the Grid definition
    'e.rtc - a pointer variable that is passed to all server side events
    'e.__si - state information
    'e.ops = misc properties that were defined in the builder for the image upload action
    
    'Your code can change the value of e.targetFileName. If you do change this value, the uploaded image will be stored in the filename specified by the new value in e.targetFileName
    'IMPORTANT: The transformation expression (defined in Action Javascript at design time) will be applied to whatever value is in e.targetFilename. So, if your event handler
    'changes the value in e.targetFilename, the transformation expression is applied to this new value.
    
    
    'Optional - your code can set a value for e.storedValue property in the e object
    'If you set the e.storedValue property, this value will be stored in the target field in the record (and the transformation expression will be ignored)
    debug(1)
    
    dim pfx as c = e.formData.V.R1.RQID
    dim fnm as c = e.ops._fileOriginalName
    dim fld as c = e.ops._uploadFolder
    
    dim nwn as c = fld + chr(92) + pfx + "-" +fnm
    
    e.targetFileName = nwn
    	
    end function
    Within that function you could also use SQL to store that field somewhere else (I'm not sure exactly what you are describing when you asay that "doc_loc" is a separate component?

    If it's just a seperate field, you can easily put it into that field with some javascript client side or by making the calculated field expression equal to whatever your attached filename field is.

    There are quite a few ways to do this but to solve your issue we will need a lot more information.

    Comment


      #3
      Re: From Xbasic Function to component

      Thanks Jinx,


      The Xbasic function uploads an applicants resume (which works well). The field in the function is completeFileName = "C:\Tracker_Moama\Tracker_moama_data\All_Documents\Applicants" + chr(92) + fileNameOnServer (this is all good).

      I simply wish to place this Xbasic function field ("completeFileName") into a field in the UX component called "doc_loc" so when I save my file to the SQL database it includes the full address of the applicants resume that they uploaded. The question is what is the code to let Doc_loc = completeFileName.

      Thanks Olaf

      Comment


        #4
        Re: From Xbasic Function to component

        I'm on my phone at the moment but something like this:
        Code:
         YourFunctionName = "{dialog.object}.setValue('Doc_Loc','"+completeFileName+"');"
        end function
        At the end of your xbasic should work assuming that completeFileName is the name of the variable with your xbasic-computed file path. You can return JavaScript back to the client in this manner.

        If you are using the built-in action JavaScript for a file upload though, this should be even easier as you can bind the file upload "field" in your UX.

        If you don't solve it by then, I'll show you when I get back to work tomorrow.
        Last edited by -Jinx-; 04-14-2016, 10:01 PM.

        Comment


          #5
          Re: From Xbasic Function to component

          Jinx,
          I am still not seeing it.

          I simply need to set a value from a field called completefilename in the Xbasic function to a field on the client side called doc_loc from within the function. The code is

          function xb_afterUpload as v (e as p)
          'This function is called after the file(s) selected in the Upload Files dialog have been uploaded to the server.
          'The function is responsible for processing each uploaded file.
          'debug(1)

          dim fileNameOnServer as c = ""
          if eval_valid("e.formData.V.R1.FILENAMEONSERVER") then
          fileNameOnServer = e.formData.V.R1.FILENAMEONSERVER
          end if

          dim extension as c
          extension = file.filename_parse(e.fileArray[1].filename,"e")
          if fileNameOnServer = "<default>" then
          fileNameOnServer = e.fileArray[1].filename
          else
          fileNameOnServer = file.filename_parse(fileNameOnServer,"N") + extension
          end if

          dim completeFileName as c
          completeFileName = "C:\Tracker_Moama\Tracker_moama_data\All_Documents\Applicants" + chr(92) + fileNameOnServer

          file.filename_parse(ext,"N") = completeFileName

          let e.data.doc_loc = completeFileName
          file.From_blob(completeFileName,e.fileArray[1].data)


          e.javascript = "alert('Uploaded file was saved on the server to: " + js_escape(completeFileName) + "');"
          'code from jinx

          '{dialog.object}.setValue('Doc_Loc','"+completeFileName+"');'I just need to set the value in the client field Doc_Loc
          end function

          Comment


            #6
            Re: From Xbasic Function to component

            Ah, posting your code helps.... With alpha, there are so many ways to skin the proverbial cat that it's hard to understand without the actual code. What I wrote above returns JavaScript to the client. So can the e.javascript variable.

            Try this:
            Code:
            e.javascript = "alert('Uploaded file was saved on the server to: " + js_escape(completeFileName) + "');{dialog.object}.setValue('Doc_Loc','"+completeFileName+"');"
            Hopefully the syntax is right. I'm on my phone instead of a computer.

            Comment


              #7
              Re: From Xbasic Function to component

              Thanks Jinx,
              Your last bit of code prefixed by window.parent.{dialog.object}.setValue('Doc_Loc','"+completeFileName+"');" did the trick
              Many Thanks
              Olaf

              Comment

              Working...
              X