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

Filter Grid Quick Search by login name

  • Filter
  • Time
  • Show
Clear All
new posts

  • Filter Grid Quick Search by login name

    I want to be able to filter the quick search choices on my grid to only include records that contain the user_id (which has the same value as the ulink field) of the user who just logged in on the previous page.

    i.e. = "rep_id = session.ulink .and. unique_key_value()"

    but I cannot figure out how to use a session variable in that filter.
    Lee Goldberg
    Software Development and Sales
    Shore Consultants Ltd.

  • #2
    Re: Filter Grid Quick Search by login name

    rep_id = "session.ulink"
    You must include the quotes.
    Insanity: doing the same thing over and over again and expecting different results.
    Albert Einstein, (attributed)
    US (German-born) physicist (1879 - 1955)


    • #3
      Re: Filter Grid Quick Search by login name

      - Unless I dont understand the question, the answer [rep_id = "session.ulink"] is incorrect**, it would be [rep_id = session.ulink]. But that isn't going to work either, see below. "session.ulink" is the WORD "session.ulink", not the value of the variable named session.ulink.

      - The function unique_key_value() has no role at all.

      - proper design says you cannot use session.ulink as your security variable. That is a normal, non-protected variable. If I had an account, I could log in, and then enter a URL like this or depending on if your ulink is an email or value, and see someone elses records. You must use session.__protected__ulink to defeat that security issue.

      - you cannot filter what the quick search returns, only what your users are allowed to ask for in the quick search. In some cases that might yield what you want, but you are not filtering what is being returned.

      - if you do use session.unlink to define the list, your dropdown, radio or checkbox would use Variable, and the variable would be set in OnGridInitialize event, maybe like this:

      e.rtc.mylist = table.external_record_content_get("mytable","myfield","","userid="+quote(e.rv.session.ulink"))

      The way you worded your question, this might actually be what you want to do.

      - Finally, the ulink value should not be the users user_id value. I mean it can be, but it shouldn't be.

      **Edit: Someone recently mentioned a situation where they got some filter to work by using quotes as describe here, but if that is true, it is a bug.
      Steve Wood
      There is no Cloud. It's just someone else's computer.
      Web - Mobile - Hosting - Products - Frameworks - Developer Resources
      AlphaToGo | IADN (100% Alpha Anywhere Websites)


      • #4
        Re: Filter Grid Quick Search by login name

        I think my issue is related. I'm trying to have fields in the Search component (not Quick Search) to filter its results based on a protected session variable (in my case its called session.__protected__ulink). I've used this session variable to filter all kinds of regular grids without issue but the sql builder in the search component (I use the "Expert" tab) doesn't work like the grid query aruguments section that I've been using over the last few months.

        The help on the screen seems to indicate that you can simply use an existing session variable in the where clause. This session variable is successfully being used by the grid that I'm trying to apply a search filter on ..

        What am I doing wrong here? I've searched these forums and wiki without success.

        I've attached a picture that shows the setup and resulting error message.


        • #5
          Re: Filter Grid Quick Search by login name

          Follow up to my earlier post .. I noticed the following in the latest release notes.

          Choice Lists for Dropdownboxes, Radio Buttons and Checkboxes - .dbf Tables - Filters - Session Variables - If you use a session variable in a filter for a .dbf table, you can now use either of these syntaxes:

          state = session.state

          state = "session.state"

          Note: In one case the session variable is quoted. In the other case, it is not quoted.
          Does this mean that filtering Dropdownboxes, Radio Buttons and Checkboxes using a session variable only works when using DBF?


          • #6
            Re: Filter Grid Quick Search by login name

            I was just looking for a solution to this issue myself when I seem to have stumbled across the answer just fiddling around with the query builder.

            Originally, I was using the genie to do all of the work and try to add the arguments that I need, but typically most things entered into the Value/Expression field would be treated like a String; my session variable included.
            Halfway through writing this post, however, I realised that I could enter my own line into the SQL statement in the query view, so I added my own WHERE:

            WHERE asmid = session.__protected__userid
            Works no problem!