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

list1 - list2 - list3 (issue with filter for list3)

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

    list1 - list2 - list3 (issue with filter for list3)

    I have 3 lists parent - child - grandchild.
    Each returns primary keys - these are assigned to the arguments: argument_key1, argument_key2 and argument_key3
    The key fields are say INVOICE_ID, INVOICE_LINE and INVOICE_DETAIL as follows
    parent - key INVOICE_ID
    child - key INVOICE_ID, INVOICE_LINE
    grandchild - INVOICE_ID, INVOICE_LINE and INVOICE_DETAIL
    When I specify that the parent of list2 is list1 - the filter works great and details are shown when I move from list1 to list2 panel.
    Filter: INVOICE_ID = :argument_key1
    So for so good.

    BUT for list2 and list3
    The filter is really creating a problem, and I am required to provide the key as I have specified the parent of list3 as list2
    (wish to go by book and specify this relation as specified above- to avoid work-arounds)
    When I assign the filter as INVOICE_ID + '|||' + INVOICE_LINE = :argument_key1
    for some unknown to me reason - it is converted to ((INVOICE_ID + '|||') + INVOICE_LINE) = :argument_key2

    Please help.

    #2
    Re: list1 - list2 - list3 (issue with filter for list3)

    Put together a sample UX component with Lists and static data and we can have a look.

    Comment


      #3
      Re: list1 - list2 - list3 (issue with filter for list3)

      Thanks - please see the attached UX! (NOTE: I replaced the old UX about 5 minutes ago - as the old one was not the latest (did not have list3 showing list2 as parent))

      As mentioned - On list2 the filter I used is
      INVOICE_ID = :my_key_from_list1
      The above works great.

      But the following has problems.
      On list3 the filter I used is (since the key field are seperated by '|||' for Primary key returned by list)
      INVOICE_ID + '|||' + LINE_NBR = :my_key_from_list2
      It is automatically changing this to
      ((INVOICE_ID + '|||') + LINE_NBR) = :my_key_from_list2

      I wish all three of this lists to return the primary key because, I am using the keys else where (in other words do not wish to use the work around to replace the "return value" of list2 to field:LINE_NBR instead of existing PrimaryKey) Note: INVOICE_ID is char, LINE_NBR is a number (is the number (int) messing it up - but the field LINE_NBR is a number and used by other applications).

      TEST_LIST1_UX1.a5wcmp

      create_tables_for_list1_list2_list3.txt

      data_for_tables_for_list1_list2_list3.txt
      Attached Files
      Last edited by JPMPA; 04-08-2014, 04:05 PM. Reason: Replaced the old UX

      Comment


        #4
        Re: list1 - list2 - list3 (issue with filter for list3)

        The trick to this stuff is to stay inside the SQL Genie until you get a valid result... using any of the SQL means to get that result. Using this SQL Statement seems to get the results you need...

        Code:
        SELECT INVOICE_ID, LINE_NBR, LINE_DETAIL, AMOUNT3, DESCRIPTION3 
        FROM INVOICE_DETAIL 
        WHERE (( Convert( nvarchar(50) , INVOICE_ID)  + '|||') +  Convert( nvarchar(50) , LINE_NBR) ) = :my_key_from_list2

        Comment


          #5
          Re: list1 - list2 - list3 (issue with filter for list3)

          Thanks David. This was exactly what I was looking for!

          Comment


            #6
            Re: list1 - list2 - list3 (issue with filter for list3)

            I changed the logic little bit so that it will use the index correctly. [field1|||field2|||field3 apparently did not use the index even though had index for these primary fields - was looking for individual values as below]. This is for SQL Server - basically extracts the field1 and field2, etc from the concatenated value separated by '|||' using SUBSTRING, CHARINDEX etc.

            With 2 field primary keys - filter
            INVOICE_ID = SUBSTRING(:my_key_from_list1, 1, ( CHARINDEX('|||', :my_key_from_list1) - 1)) AND LINE_NBR = SUBSTRING(:my_key_from_list1, ( CHARINDEX('|||', :my_key_from_list1) + 3), 100)
            With 3 field primary keys - filter
            INVOICE_ID = SUBSTRING(:my_key_from_list2, 1, ( CHARINDEX('|||', :my_key_from_list2) - 1)) AND LINE_NBR = SUBSTRING( SUBSTRING(:my_key_from_list2, ( CHARINDEX('|||', :my_key_from_list2) + 3), 100) , 1, ( CHARINDEX('|||', SUBSTRING(:my_key_from_list2, ( CHARINDEX('|||', :my_key_from_list2) + 3), 100) ) - 1)) AND DETAIL_LINE_NBR = SUBSTRING( SUBSTRING(:my_key_from_list2, ( CHARINDEX('|||', :my_key_from_list2) + 3), 100) , ( CHARINDEX('|||', SUBSTRING(:my_key_from_list2, ( CHARINDEX('|||', :my_key_from_list2) + 3), 100) ) + 3), 100)
            Thanks.

            Comment


              #7
              Re: list1 - list2 - list3 (issue with filter for list3)

              Just to set the records straight. The above theoretically looks correct. The response was actually bad for small data when tested. May be for very large data it will work better compared to previous filter clause. Thanks!

              Comment

              Working...
              X