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



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

Javascipt Onclick Not Functioning on Production Server but working on Test Server

  • Filter
  • Time
  • Show
Clear All
new posts

    Javascipt Onclick Not Functioning on Production Server but working on Test Server


    I am working with an application developer who has developed and is publishing an internal application via Alpha Anywhere. When they push the application to our test server, the Javascript onclick functionality is working as designed. However, when the same application is pushed to our production server, the Javascript onclick functionality no longer works in certain areas. More specifically - there are several picklist and value fields that upon updating should be reflected in the text to the right side of the fields (please see attached for more detail on this).

    Any help or advice on troubleshooting this should be greatly appreciated. There is no difference in the application's code, just publishing to different servers.

    Thanks in advance,


    You do not have permission to view this gallery.
    This gallery has 1 photos.

    Make sure every machine is using the same Alpha build.


      Originally posted by Pizzadude View Post
      Make sure every machine is using the same Alpha build.
      Thanks, I checked and the developer said: "It says the build version on one of the auto generated pages, and I matched the build with the one that I am using but didn't see any changes in the errors"

      Are we missing something on ensuring the same Alpha build is used?


        In the development version of AA, go to Help > About Alpha Anywhere to see the build number. If using the AA web application server, open the server settings and the build number is at the top of the screen. If using IIS, in IIS select the Site > Application Server build.


          christappan When we open the app in the Remote Testing (i.e. on the AA Web Application Server), everything is functioning as designed. However, when we PUBLISH it to the Production server, this is when the javascript OnClick functions error out.


            Are you running two web application servers, one for testing and one for production?


              Pizzadude Yes we are. We have one test server and one production server and are publishing the same app from AA onto each. The JavaScript functionality works on our internal test server but not when published on the production server. We have IT looking further, but as of now, they are saying both servers are set up exactly the same.


                Did you confirm that AA build numbers all match as I described?

                After confirming that, go to your site on a browser. Hit F12 to bring up Developer Options. The two most useful tabs are
                Console shows all the Javascript warnings and errors
                Network shows all the communication between the browser and server

                If you (or Alpha) have any "debugger;" lines in your Javascript, the Sources tab will open up whenever those lines are reached in the code. You can use the little play icon at the top right to run the code to the next "debugger;" line, or you can click the "Deactivate breakpoints" icon to the right to ignore these "debugger;" lines.

                I would start with the Network tab. If for some reason some kind of Javascript source isn't being downloaded like it should be, it would show here as an error. Then you could try to figure out why.