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

UX Fails to load after Upgrade to Build 6315 5397

  • Filter
  • Time
  • Show
Clear All
new posts

  • UX Fails to load after Upgrade to Build 6315 5397

    I have an older UX, originally built in Alpha v.11. Been working fine until upgrading to the latest official release.

    I installed the hotfixes.

    The UX is running in a tabbed UI. It throws a javascript error...


    The line 2835 in the console is:

    It works fine in build 6311 5396.

    I'm not sure how to track this down, and I'm not looking forward to re-creating the UX from scratch.

  • #2
    Re: UX Fails to load after Upgrade to Build 6315 5397


    I doubt this is 'your' issue. I also tried build 6315 and had various UX components not opening. In fact, I had all sorts of issues including publishing issues, I went back to build 6232 and everything works fine.
    Unfortunately, I just didn't have time to spend trying to reproduce a case to submit.
    Alpha Anywhere v12. Build 7582-5569 IIS v10.0 on Windows Server 2019 Std in Hyper-V


    • #3
      Re: UX Fails to load after Upgrade to Build 6315 5397

      Yeah, this has not gone well for us. While Alpha's been very responsive, I still have a whole bunch of problems with UX loading. And I'm now on today's pre-release 6333.

      Many of my errors are:

      Uncaught TypeError: Cannot read property 'controlType' of undefined

      And I can't figure out why - yet.


      • #4
        Re: UX Fails to load after Upgrade to Build 6315 5397

        In that case I am not going to spend time trying to fix this. I will stay with the older build for now.

        I was looking forward to some issues that were a problem with 6311 5396, that are actually fixed in 6315 5397.

        Anyone tried build 6311 5396, released 12/9/19?


        • #5
          Re: UX Fails to load after Upgrade to Build 6315 5397

          If only Alpha could do something like... I don't know... maybe download their own releases... and... let me think... maybe test them? I know it sounds radical... and I know that "Alpha's been very responsive"... but maybe... just maybe... if Alpha put away the matches... and stopped starting fires... they wouldn't have to be so "responsive" in putting them out.

          Alpha puts out a release... but they never actually download that release and test what they just fixed... or added. It's quite mind boggling that they don't. Have a nice normal PC sitting in a corner, download the release like we all do, install it, test what changed. Doing this before a release is public would catch a bucket of problems that developers have to fight with.

          I know this is not going to be a popular notion as I know you all like looking forward to yet another round of hot fixes and non-useable pre-releases. 2 "official" releases last week... both with hot fixes... c'mon... this can be better.


          • #6
            Re: UX Fails to load after Upgrade to Build 6315 5397

            I am having intermittent report printing issues, some fields (not all, numeric don't seem to be affected) fail to print on the single page report. If I go back and print a previous report and find one that prints correctly, then I can print the current report fully rendered.

            I am not sure how I would present a test case for something like this but I am tempted to create a video to show that it is happening. Also tried 6331 and 6333 with the same issues, going back to 6276 seems to sort it out.


            • #7
              Re: UX Fails to load after Upgrade to Build 6315 5397

              I have not put the new release in production but have tested it on my development machine. I found I had to dirty some UX components and save them to make them work. There was no pattern to the problem so I ruled out moving to the new release until that is resolved. I don't have time to test every single component (large project) and I have some mission critical ones running right now with Stripe integration....can't afford to have them become unresponsive with lost revenue.

              Testing is an essential part of the process.....I am not sure why these issues are making it into the official release. It forces us to use hot fixes or a pre-release that is not approved for production......yet we are enticed by the new features that have been added to the new release. Frustrating for sure.
              Last edited by gregincolumbus; 12-17-2019, 12:41 PM.


              • #8
                Re: UX Fails to load after Upgrade to Build 6315 5397

                I am bumping this thread to see if anyone has found a solution to the issues described other than rolling back to a previous version. There are numerous new features in Build 6315 5397 I would like to implement but only UX components function as expected.


                • #9
                  Re: UX Fails to load after Upgrade to Build 6315 5397

                  I have found 2 temporary workarounds for the latest release, both have hotfixes that appear to also fix the issue.

                  If you don't want to try the hotfixes, here are your options.

                  1) If you get a UX that throws a javascript error in working preview and that won't load in production, you can add an argument to the ux with no value. This will fix that issue.
                  2) The second issue, if you get an Invalid Expression in a control then I found that adding a default value of the empty string (2 double quotes) fixes that issue.


                  • #10
                    Re: UX Fails to load after Upgrade to Build 6315 5397

                    Thank you for the tips Jeremy...those are very helpful to know.

                    I would prefer not to use temporary workarounds since my project is simply too large but it is nice to know that you found a way to overcome the issues.

                    Guess I will have to ride this version out again and hope the next one fixes the problem....I am paying too much on my subscription to be taking that approach for very long though.


                    • #11
                      Re: UX Fails to load after Upgrade to Build 6315 5397

                      Several of my UX components didn't load. One or two (or both) things often fixed this:

                      1. Just edit, save and republish the component in the current build.
                      2. Edit the component, use Menu / Recalculate All Controls, save and republish.

                      UX components with repeating sections have been especially affected. If you're working through these problems and you have repeating sections, you're probably well off to install the latest pre-release. In fact, I'm doing that for various reasons tomorrow, on Friday.


                      • #12
                        Re: UX Fails to load after Upgrade to Build 6315 5397

                        In a large project this type of fix is too time consuming... and there is no proof it would work every time.

                        Something very bad has happened in 6315. I wish Alpha would tell us what it is. Since that won't happen, all you could do is try a pre-release and pray. Maybe that's what Alpha does upon every single new release.


                        • #13
                          Re: UX Fails to load after Upgrade to Build 6315 5397

                          Is there anywhere in the release notes or pre-release notes that lists the bugs that are fixed with that particular build?

                          I know there are general type statements (ie. fixed a regression with "abc") but is there a line item type list? If not, that would be a great thing to add to the notes as a way to reassure developers that a particular build addresses a specific problem they have experienced. I know this would require extra time for Alpha to implement but the return on that investment of time would definitely be of great benefit to developers.


                          • #14
                            Re: UX Fails to load after Upgrade to Build 6315 5397

                            There are often pre-releases with no notes at all. No new items, no bug fix notes (sorry... regressions) so there's no way of knowing if a pre-release is going to help. It seems this "official" and pre-release situation is getting worse.


                            • #15
                              Re: UX Fails to load after Upgrade to Build 6315 5397

                              I have given up.

                              My lists have been screwed up by Alpha since July - worked with them to find the problems, was assured that 6332 would fix. It did not - it's way too much to expect going through all applications and components to rebuild lists. Will be moving all operations to a different platform in January.