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

Split menu hierarchical list - move from static to SQL list actions?

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

  • Split menu hierarchical list - move from static to SQL list actions?

    The video's show a very easy way to create a 'split menu hierarchical menu' using a static list of menu titles. However this functionality stops one step too soon for my skills. The pik shows the structure I have to date, ie clicking "My Cases" leads to "Open cases." A companion list is going to be "Closed cases." Obviously these two menu items are dynamic, ie on one day a case will be open and appear on one list, and two days later it'll be closed and appear on the other.

    StaticAction1Pik.PNG

    At the moment the endpoint is "Action_1." Can someone explain how I can get "Action_1" to be a SQL defined list, ie all open cases. I have the SQL, I'm just not sure how/where to put it to work in this great component.

    The user will select from the list of open case titles (SQL generated), and the new endpoint action (now Action_1 presumably) will point to the embedded UX which displays the details of the specific case - ie filtered by the argCaseNumber.

    I hope this makes sense.

    Of course, I might be looking in the wrong place and there's a more effective alternative to this component - although it it just too good to walk away from easily.

    If someone could guide me through this it'd be a great help.

    Cheers

    Malcolm

  • #2
    Re: Split menu hierarchical list - move from static to SQL list actions?

    To which video are you referring?

    Would this video help you? UXL_V12--71

    Not quite sure what you're after. A sql-based List with 2 selections... Open Cases and Closed Cases. Selecting one of these choices will expand the List and show the cases for that choice. Selecting one of those cases will take you to an embedded component showing that case. Is that right?

    Comment


    • #3
      Re: Split menu hierarchical list - move from static to SQL list actions?

      Ah! Thanks for the pointer to the second video - that's the second clue to the adventure. I now need to mix both static menu items (for the first two steps), with dynamic items for the last step. Once it's done, hopefully, I'll post the result. Thanks again for the prompt. Malcolm

      Comment


      • #4
        Re: Split menu hierarchical list - move from static to SQL list actions?

        So, I got a bit further. What I'm after is a menu structure like this:

        My Cases (static)
        ........Open Cases (static)
        ..............Case 1 title (sql)
        ......................Case details (UX)
        ..............Case 2 title (sql)
        ......................Case details (UX)
        Closed Cases (static)
        ..............Case 4 title (sql)
        .......................Case details (UX)
        ..............Case 5 title (sql)
        .......................Case details (UX)

        I can arrange the first bit: ie

        My Cases (static)
        ..........Open Cases (static)
        ..........Closed Cases (static)

        and the following xbasic taken from video UXL V12_71 gets me the sql/dynamically selected cases names in the form

        Case 1 title
        Case 2 title etc:

        function xb_getdata as c (e as p)
        dim cn as sql::Connection

        cn.Open("::Name::CMS")
        dim sql as c
        sql = "SELECT 'My Cases', 'Open cases', CaseName FROM Cases WHERE ISNULL(CLOSEDATE)"
        dim flag as l
        cn.PortableSQLEnabled=.t.
        flag = cn.Execute(sql)
        dim rs as sql::ResultSet
        rs = cn.ResultSet
        dim txt as c
        txt = rs.ToString(-1,-1,.t.,"|")

        'debug(1)

        dim json as c
        json = a5_xbasictreetojsontree(txt,"|","display")
        xb_getdata=json
        end function

        My challenge is to get the two working together as outlined above - or am I looking for a solution in the wrong place? I'm trying to avoid nesting the second list inside the first (if that's even possible) in order to save screen space by only having one menu.

        Hopefully there's a relatively simple solution somewhere.

        Cheers

        Malcolm
        Last edited by Malcolm; 10-25-2016, 04:48 AM. Reason: layout changes

        Comment

        Working...
        X