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

Data Binding in UX w/ Repeating Section

  • Filter
  • Time
  • Show
Clear All
new posts

    Data Binding in UX w/ Repeating Section

    I have officially lost my mind. This used to be straight-forward and now I cannot see for I am blind.

    I have a UX component. One repeating section of three fields, a reset and a submit button. That is all.

    So, I create that, go to data binding. Specify the one table. Then, click the button to Bind Tables to Repeating Sections. It demands that the <Top Level> be bound to the table, and offers no choice to bind my Container_1 to to the table. So, very stuck there. How can I instruct the UX that I want to bind the table to the repeating section?

    Second issue: This is a multi-tenant app, so when I populate the repeating section at load time, I would like to supply a filter (Facility_ID = 100 for instance). Again, I cannot see where to do that.

    Sure, I could have done this in 5 minutes with a grid, but the UX is the place to be for mobile and for whatever reason I've forgotten how to do this basic stuff. Someone lend a hand?


    Re: Data Binding in UX w/ Repeating Section

    Hi Steve

    I'm pretty sure you're not losing your mind. The top level table can't be bound to a repeating section as far as I'm aware.

    Although a bit quirky, it sounds as if you could have a Facility table as your top level table, and your repeating section table linked to that in the Data Binding. You could then use {dialog.Object}.populateControlsFromTable(100) wherever it makes sense which would limit the user to just their repeating section entries.

    Hopefully I'm not losing my mind too.

    Thanks, Michael


      Re: Data Binding in UX w/ Repeating Section

      I started to wonder that. I was looking to use something other than grids for about 20 little user-maintained lists because grids don't have all the new stuff that UX/mobile has. I think expediency is going to have me putting out a lot of grids tonight.


        Re: Data Binding in UX w/ Repeating Section

        Hi Steve,

        As you are designing your UX for mobile use, I would recommend the list control over a repeating section. The repeating section has, usually, editable controls which are difficult to get to look right unless you always use the same screen width. The list control is easily configured to look great on a tablet 7 or 10 inch, iphone sized smartphone or something smaller like a samsung galaxy y, 3 inch screen (yes one of my staff has one of these, so he needs to be catered for). Then you can edit/enter new records by means of a pop-up window called by a button or double click event on the list. The list is also easily filtered by means of arguments. I am busily replacing most of my grids with list controls, the templates for freeform layouts make them look great.


          Re: Data Binding in UX w/ Repeating Section

          Thanks Lance. I agree about how nice the mobile stuff is and I'm trying to write and even convert as much as I can to the new tools. Sometimes, however, grids are still the best old tool in the box and that's largely what I've decided to go with for this week's project; most of the user action on this portion will be on desktop so it's suitable, still looks and works well.