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

script error in cascading lists in disconnected component

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

    script error in cascading lists in disconnected component

    Background:

    I've just got my first very simple 'disconnected' list with detail view up and working - that was easy.

    The problem:

    I'm now branching out to tackle a one-to-many relationship: one 'project' has many 'log entries.' The Log entry list has a detail view that displays as it should.

    The video's show the working end of this situation, but not how it's set up - so I've gone ahead and tried cascading lists:

    Parent list: Projects
    Child list with detail: Log entries.

    The fields display correctly, the save works OK in 'working preview,' the little orange triangle appears - and never leaves and the synchro button throws up 'an error has occurred in the script on this page...'


    Advice:

    Are cascading lists the appropriate approach? Is there something else I'm missing?

    Thanks Malcolm

    #2
    Re: script error in cascading lists in disconnected component

    Hi Malcolm,

    Have you tried live preview to get a better message ? Maybe try to recalculate the controls.

    Ken

    Comment


      #3
      Re: script error in cascading lists in disconnected component

      Thanks Ken,

      At least the script error disappeared on the live preview and now the local server.

      When publishing it to the local server, 'save' has no effect on the dirty record (but it does disable the button), and 'synchronize' actually pushes the edit to the server - but the little orange triangle remains firmly in place. Getting there - but oh, so slowly...

      Ta

      Comment


        #4
        Re: script error in cascading lists in disconnected component

        Originally posted by Malcolm View Post
        Thanks Ken,

        At least the script error disappeared on the live preview and now the local server.

        When publishing it to the local server, 'save' has no effect on the dirty record (but it does disable the button), and 'synchronize' actually pushes the edit to the server - but the little orange triangle remains firmly in place. Getting there - but oh, so slowly...

        Ta
        Are you using the latest pre-release? I would try to build a stripped down UX component from scratch and see if you get the same thing. I had the same issues with an application I was building and I found errors in my xbasic validation as I traced through and some javascript issues. Some errors in coding are the reason the orange triangle is not disappearing. If you have a detail view make sure the fields you are updating are all accounted for, and, the list control shows no errors in design mode.

        Comment


          #5
          Re: script error in cascading lists in disconnected component

          Here's the problem and the solution - straight from the wizards at Alpha:

          The parent list opens the child list, which is editable. When the detail is finally saved to the database with Synch, the synch code tries to update the parent list first to make sure there is a record to match the child record. The problem is caused by the return value in the parent list being set to "field"

          What happens is the code can't find the parent record using field, so the update fails. However, if you set the return value to "PrimaryKey" (which is the same field), then the update code can find a parent record and verify it exists.

          The complicating factor in fixing this is the the data in native storage is still looking for a field value, so the local storage must be cleared to make the change to the list.

          To find out how to clear local storage, click on "Overview" on the left menu for the UX. There is a link at the bottom that opens documentation on using native storage. In the documentation look for managing local storage.

          would be
          1) Set the return value in the parent list to Primary Key.
          2) Add a button to clear local storage. The code on the button is:
          var obj = {dialog.object}._ls_getData('a');
          {dialog.object}._ls_deleteKeys(obj);
          3) Clear the local data where ever necessary. (on all devices that you have used with the system.)
          4) Remove (or hide) the temporary button.
          5) TEST - everything should work properly now.

          Comment

          Working...
          X