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

Conditionally filter a list

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

    Conditionally filter a list

    In this list on a UX, records will be filtered by a login variable, clientid. Specifying the filter as Clientid = :CLIENTID works fine. But I would also like to have a super user that can see all records. The filer building box does not have an editor that evaluates the filter, but this certainly does not work.
    if( :CLIENTID = 0 , '', Clientid = :CLIENTID )

    Is there an approach that will let me either filter the list by clientid or not?

    Bill.

    #2
    Re: Conditionally filter a list

    A couple ways Bill.

    First, you can populate the list from an Xbasic function. I've taken to doing this almost by default these days because people keep asking for more changes, more considerations, more filters. Keep in mind that the JSON generated by Xbasic needs to match the field definitions in the list -- including case sensitivity.

    A second way is to use the onDialogExecute event where you can change the e.tmpl like this:

    Code:
    if eval_valid("MyVariable")
    	if MyVariable <> "0"
    		sqlTemplate = <<%a%
    			CustomQueryHere
    		%a%
    		e.tmpl.page_fields[21].v.LIST1.sql.sqlstatement = sqlTemplate
    	end if
    end if
    You'll need the correct array index and name of course - you can find this by choosing the Xbasic tab at the very very bottom of your UX designer.
    -Steve
    sigpic

    Comment


      #3
      Re: Conditionally filter a list

      Bill, does this list have a detail view associated with it?

      Comment


        #4
        Re: Conditionally filter a list

        Steve, at first blush, populating via xbasic sounds attractive.

        Lee, I'll show my newness to this. I do have an OnDblClick event that opens a UX detail parent-child view of the record. But the list itself does not have a "detail view" does it?

        Comment


          #5
          Re: Conditionally filter a list

          I was hoping you'd say that. There is an easy way to do this. In the list control, you can use the Custom/Xbasic function. It runs before the lists loads.

          Comment


            #6
            Re: Conditionally filter a list

            Bill - one of the most popular genies in Alpha is the list building genie. Add a new control, but while still in the Add dialog, click the "List Control - Quick Setup Genie" at the bottom of the dialog. It's not everything, but it's pretty helpful and makes the building of a list control with detail a lot easier.
            -Steve
            sigpic

            Comment


              #7
              Re: Conditionally filter a list

              Thanks guys. Off to explore.

              Comment


                #8
                Re: Conditionally filter a list

                Alpha gives you an easy way of doing this. But I have to make the assumption that your login variable is a session variable. If it's not a session variable then post what it is and how you set it.

                If it is a session variable then, in your List Control, Data Source tab, "Server side beforeQuery event", add the word checkUser. This will be an XBasic function that Alpha will call. If you click the Builder for this event you'll see how you can create it. The function can be named anything you like... I named it checkUser.

                In the XBasic functions section of the UX... add this function... which, except for my code, was created by Alpha.

                Code:
                function checkUser as v (e as p)
                	
                'debug(1)	
                'Fires before the query to retrieve List data is executed. You can use this event to authorize the query
                'If the query is not authorized, it will not return any data
                'The e object that is passed in includes:
                'e.tmpl = UX definition
                'e.sql - the SQL statement that will be executed
                'e.arguments - SQL argument values to be passed to the SQL statement
                'e.listProperties - properties of the List control
                
                'Your code can set these properties:
                'e.authorized - set to .t. or .f.. If you do not set e.authorized, it is assumed to be .t.. If e.authorized = .f., the query will not return any data.
                
                'Your code can modify the SQL and the arguments used in the List query. For example:
                'e.sql = "Select id, firstname, lastname from customers where id = :whatid "
                'e.arguments.add("whatId",23)
                
                if session.clientid = 0 then
                	e.sql = "SELECT PersonId, Clientid, FirstName, MiddleName, LastName, Address1, City, St, Zip, Latitude, Longitude, ChargeAmount, AdjustmentAmount, PaidHereAmount, OnholdAmount, OnholdDate, CurrentBalance, Addr_Quality FROM Person WHERE Clientid IS NOT NULL"
                end if	
                
                
                end function
                My code is the "if" statement. If your session var clientid is 0, then your e.sql statement will include WHERE Clientid IS NOT NULL... which should pick up everything.
                If your clientid is, for example, 12, then your List's SQL Statement will not change. This is assuming your List has the filter Clientid = :CLIENTID

                The nice bit about all this is that there is no extra callback. Your List is going to get data... and we're just taking a quick detour to either change the SQL statement... or not.
                Last edited by Davidk; 05-09-2019, 05:59 PM.

                Comment

                Working...
                X