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
Devcon 2020 Goes Virtual! LEARN MORE >

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

UX Data Binding [Master-Detail-Detail or Parent-Child-Grandchild table setup]

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    UX Data Binding [Master-Detail-Detail or Parent-Child-Grandchild table setup]

    I am not using GRID for a reason, but trying to use UX with 2 repeating containers [detail1 and detail2] of an existing master-detail1-detail2 [parent-child-grandchild] on a SQL database table setup.
    The tables have one to many relationship as per the business requirement.
    But unfortunately getting the following error while I am doing the data binding on the UX component.

    "All OneToMany links in the UX must be linked to a table in the <Top Level> of the UX.
    The following OneToMany link is linked to a field in OneToMany linked table.
    This is not supported. <Table name: DETAIL2...>"

    I was hoping to use this Data Binding on the UX component under the assumption that Alpha delivered delete button (and add) on the repeating container will take care of the cascading - example deleting the master record will delete the details from both detail1 and detail2 records. Or deleting a record/row from detail1 will delete the corresponding detail rows in the detail2 table. Does this mean I will have to manually create the code to delete the rows in detail1 and detail2.

    Question: Do I have to manually write code to delete the corresponding rows from the detail1 [Child] and detail2 [Grandchild] tables when user deletes a row from the Master [Parent] table.

    If you have done similar project - please provide some help. Thanks!
    Tags: None
    #2
    Re: UX Data Binding [Master-Detail-Detail or Parent-Child-Grandchild table setup]

    Are you using MS SQL? If so, you can build those rules at the database level.

    Comment

      #3
      Re: UX Data Binding [Master-Detail-Detail or Parent-Child-Grandchild table setup]

      Thanks. I do have the tables built (those existed from years) - this (mobile app) is a new user interface to that application.
      On the database level we do show the master detail primary keys, etc. But do not depend on its database engine to do the cascade delete, or any other database specific logic - so as to leave it portable (do no use too many feature of the database - because in the future if we change to a different database, it may not work or may not have that feature. Our application needs to do all the logic.)

      I am trying to understand what to expect from Alpha. In most of the application development that I have done, the software has the in-build logic that do the tasks like this (like the above example: when the master row is deleted - it automatically deletes the details rows for that key, etc)

      In Alpha Anywhere, if I delete the master row does the fact that we provided the link to the details also automatically delete the details rows also.
      Or do I need to write logic where in the loop all the detail rows need to be programatically deleted.

      In Alpha, I have tried this using the a) lists, b) UX controls specifying the parent/keys in details, c) Grid with parent/linked information, where Alpha does query the detail records automatically, i.e., whenever the master row is queried - but it does not do a cascade delete to the detail rows, whenever the master row is deleted.

      I do not mind writing the code to delete the detail rows whenever the master row is deleted. But, I wish to confirm from the experts one of the following:
      1) Alpha really does not do a cascade delete in Lists, UX controls, and Grids - so we have to write the code to do that.
      OR
      2) Alpha does the cascading delete - I may just be missing some setup?

      Thanks!

      Comment

        #4
        Re: UX Data Binding [Master-Detail-Detail or Parent-Child-Grandchild table setup]

        I may have missed it too, but I don't think Alpha handles cascading deletes. I would write code to handle it. I'm heard of others designing their apps to be portable for other databases, but I've never really seen it happen. I used to use Clarion which was portable on the compiler level. Flip a switch and it can use another database. Nobody that I knew ever flipped the switch. I've worked on big projects taking data from a PeopleSoft Oracle database to a SQL database, even though the data was the same the software wasn't... It seems like you don't get to utilize all the power and features of the database coding with that premise. Good Luck with your app.

        Comment

          #5
          Re: UX Data Binding [Master-Detail-Detail or Parent-Child-Grandchild table setup]

          Ok Thanks. I appreciate your time.

          Comment

            #6
            Re: UX Data Binding [Master-Detail-Detail or Parent-Child-Grandchild table setup]

            Hi Lee, After failing to figure out doing the cascade delete automatically in the app without writing too much code, I finally settled for your suggestion to use the database's cascade delete. Thanks you for the help.

            Comment

              #7
              Re: UX Data Binding [Master-Detail-Detail or Parent-Child-Grandchild table setup]

              Hi all, does any one knows what to bind two sets of text controls to two different tables?? ex.. one set of controls is bind to the customer table and the other set of controls are bind to another table within the same mobile app??

              Comment

              Previous template Next
              Working...
              X