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

Action Javascript error from upgrading

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

    Action Javascript error from upgrading

    Hi Everyone,

    Running into an issue with one of my UX compnents after an upgrade I did from 12.4.5.1 4770-5018 to 12.4.6.0.1 5887-5315 and the action javascript it runs.

    The action javascript itself is pretty simple, I am just using the built in Get-Server side data to get data from a table not referenced in the data bindings so I can set a field value on the onRenderComplete client-side event. When I ran the update for both the application server and my dev system to the version metioned above, I noticed the field not getting populated anymore, and this error showing when I try to edit the action javascript.

    Edit Action error.PNG

    So I decided that maybe due to the upgrade, the action broke somehow so I would just delete it, re create it and try again. I do just that but the field still does not apply. I see this error show up in the web browser console output.

    new error.PNG

    After hours of debugging, I came to the conclusion if I comment out the all to run the action javascript, I do not get this error on the browser console. I then decide to create a whole new UX component, with just enough functionality within it to replicate what the single field is doing with the action javascript and it works. I would hate to have to rebuild the entire component over again in another file just because of this issue and am hoping someone on here may know what is going on.

    Here is the onRenderComplete javascript code (Commenting out the action to 'Get QMS Numbers' will not cause the error to show)
    OnRenderComplete.PNG

    Here is the Action javascript that runs
    recreated action.PNG

    Here is the full query that gets ran (I've tried removing the where clause in my debugging, still got the error)
    full sql query.PNG

    Thanks in advance.

    #2
    Re: Action Javascript error from upgrading

    bump

    Comment


      #3
      Re: Action Javascript error from upgrading

      Here are a couple of things to try.

      While viewing the controls, click on the Controls Menu dropdown and choose Recalculate all controls. See if that helps.
      Next, add a button to your UX and run the Action from there. Add onSuccess code to the action...

      Code:
      debugger;
      var myData = {dialog.object}._serverSideData;
      Then, Inspect the page before you click that button and see what's in the debugger. Are you getting results from the Action?

      The error you're seeing... cannot read property 'toLowerCase' of undefined... is a very common bug in Alpha. I've see it crop up a dozen times over the last year. It keeps getting fixed in various places, but it seems quite embedded throughout Alpha code.

      In the debugger, click on that link... NCR_Form.a5w:5081... see where that takes you. Try to determine that area that's breaking.

      The main issue is that you've upgraded from a build that is 18 months old. This is a huge leap in Alpha time... which means you're battling old bugs, old bug fixes, new bugs, and sweeping changes to how things work and how code runs. I'm very surprised you've not run into more than this.
      Last edited by Davidk; 07-06-2019, 11:20 AM.

      Comment


        #4
        Re: Action Javascript error from upgrading

        Ya, I'm not getting any results back from it. Sounds like they have a history of consistently forgetting to null check objects before invoking functions of them.

        I had a feeling something would break with that large of a jump of version, so far this is the only issue I've ran into. The fact that I have to re make the component in a new file to avoid the error makes me think something in now alpha handled the action before has changed vs current embedded within the component code when interacting with the server. If my employer didn't need to take advantage of the audit tables that came out after the version they were running with I would have not upgraded. I feel like at this point it would have been more time saving for me to have just built it out myself in my own c# service and called it good.

        Comment


          #5
          Re: Action Javascript error from upgrading

          Recreating my component did not fix the issue, how ever I've been able to narrow down the bug to an issue in relation to the onRenderComplete client side script and the fact I have a image bound control in a repeating section. The script does not reference or affect the repeating section. Just submitted a bug to the devs about it. I think my work around at this point is to move the script into a button and make the user click the button to have the script execute rather than having it automatically as the load the component.

          Comment

          Working...
          X