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

Error Saving UX component

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

    Error Saving UX component

    Hello!

    I'm trying to save changes to a UX component, however, i'm getting the following error:

    Script:UI_DLG_BOX:@=genericPageBuilder_title_var_162438523
    Line 2647
    flagsave = saveComponent(wp,local_variables())
    Property not found
    wp2.page_fields[] subelement not found.


    Anyone have any idea how i fix this? or what this means?


    Thanks
    Lee

    #2
    Re: Error Saving UX component

    What build?
    Insanity: doing the same thing over and over again and expecting different results.
    Albert Einstein, (attributed)
    US (German-born) physicist (1879 - 1955)

    Comment


      #3
      Re: Error Saving UX component

      Originally posted by peteconway View Post
      What build?
      I'm using latest build of alpha anywhere.

      Comment


        #4
        Re: Error Saving UX component

        Official release?
        Insanity: doing the same thing over and over again and expecting different results.
        Albert Einstein, (attributed)
        US (German-born) physicist (1879 - 1955)

        Comment


          #5
          Re: Error Saving UX component

          Originally posted by peteconway View Post
          Official release?
          yes. Official release.

          Comment


            #6
            Re: Error Saving UX component

            This is clearly a bug. Probably only seen if you have some specific control or a control with some specific properties set on your UX. Revert to earlier versions of your UX (right click on the component in webprojects control panel & restore backup & see when it occurs. Then try to replicate it with the simplest possible ux & if you succeed send in a bug report. It will be fixed probably by the next day if not sooner & the community will be thankful to you :-)
            Frank

            Tell me and I'll forget; show me and I may remember; involve me and I'll understand

            Comment


              #7
              Re: Error Saving UX component

              Thanks I'll work on your recommendation.

              Comment


                #8
                Re: Error Saving UX component

                I run into these issues quite often. Closing the app and relaunching AA usually fixes the issue. Worst case scenario, do as Frank suggests and roll back the component to a previous version. Though, that's not always a sure thing. On rare occasions I've had to rebuild components.
                Alpha Anywhere latest pre-release

                Comment


                  #9
                  Re: Error Saving UX component

                  I wasn't able to roll back due to a file system issue and all files had the same date/time! grr... in the end i uninstalled AA and reinstalled it. I've ran into these also from time to time and I often end up just re-creating the object.
                  after reinstall of AA: It still didn't work and i couldn't find where it was erring. I'm on such a time crunch today to get this done that i just recreated to UX and thus far it's working flawlessly. I could always submit as a bug, however, the time to make an Sql back up right now is not in my time constraints for today. i have it on my list of things to do later this evening.

                  Comment


                    #10
                    Re: Error Saving UX component

                    Originally posted by leetv View Post
                    I wasn't able to roll back due to a file system issue and all files had the same date/time! grr... in the end i uninstalled AA and reinstalled it. I've ran into these also from time to time and I often end up just re-creating the object.
                    after reinstall of AA: It still didn't work and i couldn't find where it was erring. I'm on such a time crunch today to get this done that i just recreated to UX and thus far it's working flawlessly. I could always submit as a bug, however, the time to make an Sql back up right now is not in my time constraints for today. i have it on my list of things to do later this evening.
                    Submitting a bug can be hard on these problems. If you can, send it in. But a bad file doesn't necessarily lend any clues to how it happened, so the root problem may not be found. I had a similar problem occur earlier today when I changed the "Conditional Style Level" on a control from "Cell" to "Control". Alpha bugged out and wouldn't save. After a restart of AA, I could change the style level with no issues. So it's not like you can point to that property definitively and say "X happens whenever I Y".
                    Alpha Anywhere latest pre-release

                    Comment


                      #11
                      Re: Error Saving UX component

                      Originally posted by TheSmitchell View Post
                      Submitting a bug can be hard on these problems. If you can, send it in. But a bad file doesn't necessarily lend any clues to how it happened, so the root problem may not be found. I had a similar problem occur earlier today when I changed the "Conditional Style Level" on a control from "Cell" to "Control". Alpha bugged out and wouldn't save. After a restart of AA, I could change the style level with no issues. So it's not like you can point to that property definitively and say "X happens whenever I Y".
                      Thanks. I tried to re-create the issue by removing a few controls from my UX at a time and saving (to eliminate which control it is) and nothing seems to be helping. I just recreated. I'll still send a bug report, but I don't have much to give Alpha in the ways of recreating the bug. :(

                      Thanks everyone.

                      Lee

                      Comment


                        #12
                        Re: Error Saving UX component

                        Sorry I can't add any more on this.. I do in the past that if this kind thing did surface I would shut down and revert to the last working copy from the auto backups.
                        Insanity: doing the same thing over and over again and expecting different results.
                        Albert Einstein, (attributed)
                        US (German-born) physicist (1879 - 1955)

                        Comment


                          #13
                          Re: Error Saving UX component

                          It seems to me that one thing that keeps surfacing is having a hidden control as the last control in a container and or in a component. If you have any hidden fields move them up always. If you look at the release notes, and or follow pre-release versions you will see ocasional errors with this - that do get fixed ASAP. The other thing that keeps popping up are edit-combo errors. This may have nothing to do with your particular error BUT if you have either condition - a hidden field as the last control, or an edit-combo dropdown I would suggest eliminating them and test. If it is repeatable send it in as a bug otherwise it could be numerous things. When I run into an error like this on save, the first thing I do is select all objects and "copy to clipboard". Create a new UX, paste the controls and start removing them until it works. This helps find the offenders FAST.
                          NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

                          Comment

                          Working...
                          X