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

Is there a way to make [Lookup Icon] Show/Hide by a condition?

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

    Is there a way to make [Lookup Icon] Show/Hide by a condition?

    I think the Lookup feature in A5 is great. It fills in my new records fast and furious. My problem is the field that shows the Lookup Icon is always active. This means a user could easily OVERWRITE existing and good data.

    I would like the Lookup Icon to only appear for a new record or when that field is blank. Is there a way to control the Lookup Icon according to this condition?

    #2
    Re: Is there a way to make[ Lookup Icon] Show/Hide by a condition?

    You could try something like this in the enable expression: detailView.rowState = 'enter' It will be for the text box of the lookup not just the icon.
    and the Conditional Style to change the color or identify it that it is not enabled.

    Comment


      #3
      Re: Is there a way to make [Lookup Icon] Show/Hide by a condition?

      I created a workable solution to my problem with a crude but interesting methodology. As you know, the small Icon (for Lookup) is placed to the far right of the textbox field. I thought that if I couldn't turn it off, I would "cover it up".

      What I did was to use an unused text field in my table and placed it just to the right of the textbox field with the Lookup. I then made that new field 25px wide and a relative left position of -42px. This would in reality "OVERLAP" the right-side of the previous text field. Great - first problem solved. Now I needed to create a Show/Hide condition to test if my desired field was blank or not. I added this to the "fake" field. Therefore if my "real field" had data, the "fake field" SHOWED - in effect preventing a Lookup. If the "real field" was blank due to a new record, the "fake field" was hidden and exposed the Lookup Icon.

      Works like a charm and thought I'd share. Only problem is, users may wonder what that small box was doing at the end of the "real field" so I added an on click message to the "fake field" stating that Lookup was not permitted on fields that already had data.

      BTW - this was all done on a Detail View.

      Comment


        #4
        Re: Is there a way to make [Lookup Icon] Show/Hide by a condition?

        Originally posted by Fulltimer View Post
        I created a workable solution to my problem with a crude but interesting methodology. As you know, the small Icon (for Lookup) is placed to the far right of the textbox field. I thought that if I couldn't turn it off, I would "cover it up".

        What I did was to use an unused text field in my table and placed it just to the right of the textbox field with the Lookup. I then made that new field 25px wide and a relative left position of -42px. This would in reality "OVERLAP" the right-side of the previous text field. Great - first problem solved. Now I needed to create a Show/Hide condition to test if my desired field was blank or not. I added this to the "fake" field. Therefore if my "real field" had data, the "fake field" SHOWED - in effect preventing a Lookup. If the "real field" was blank due to a new record, the "fake field" was hidden and exposed the Lookup Icon.

        Works like a charm and thought I'd share. Only problem is, users may wonder what that small box was doing at the end of the "real field" so I added an on click message to the "fake field" stating that Lookup was not permitted on fields that already had data.

        BTW - this was all done on a Detail View.
        You could also use javascript to set the style.display = 'none'. Use Firebug to figure out what the ID of the element is and then plop the javascript in the appropriate loaction. I took a quick peek at some of my lookups in a grid. They appear to be of the format "{grid.componentName}.D.V.R1.<NAME OF FIELD HERE>.CUSTOMBUTTON.0" in a detail view.

        Here's a quick example of showing/hiding:
        Code:
        // Hide the element; replace FIELD_NAME_HERE with your lookup control's field name.
        $('{grid.componentName}.D.V.R1.FIELD_NAME_HERE.CUSTOMBUTTON.0').style.display = 'none';
        Code:
        // Show the element; replace FIELD_NAME_HERE with your lookup control's field name.
        $('{grid.componentName}.D.V.R1.FIELD_NAME_HERE.CUSTOMBUTTON.0').style.display = '';
        Voila! You could figure out which Detail View client side events you need to add this code in to make this happen. Or you could put it in a function call in the client-side show hide definition for your control that has the lookup. There are lots of places you could put it, actually.

        ---
        Sarah
        Alpha Anywhere latest pre-release

        Comment


          #5
          Re: Is there a way to make [Lookup Icon] Show/Hide by a condition?

          Second thought: If you really wanted to be thorough, you could modify the row html and strip out the lookup icon completely in the server-side onDetailViewRender event. This would ensure that no one could access the lookup ever because it wouldn't exist on the client side.

          UPDATE: referenced the onExistingRowRender event when onDetailViewRender is more appropriate for the situation discussed here --- hiding in a detail view.
          Alpha Anywhere latest pre-release

          Comment


            #6
            Re: Is there a way to make [Lookup Icon] Show/Hide by a condition?

            Originally posted by TheSmitchell View Post
            Here's a quick example of showing/hiding:
            Code:
            // Hide the element; replace FIELD_NAME_HERE with your lookup control's field name.
            $('{grid.componentName}.D.V.R1.FIELD_NAME_HERE.CUSTOMBUTTON.0').style.display = 'none';
            Code:
            // Show the element; replace FIELD_NAME_HERE with your lookup control's field name.
            $('{grid.componentName}.D.V.R1.FIELD_NAME_HERE.CUSTOMBUTTON.0').style.display = '';

            ---
            Sarah
            Sarah,

            Many thanks for your insightful suggestion to my situation. I elected to use your first 2 pieces of code and found them to work as described. I simply substituted my field names and it worked. I did not know this process was available. Others can surely benefit by using this technique. Thanks again!!!

            Comment

            Working...
            X