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

Does setValue mark field dirty in detail view?

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

    #16
    Re: Does setValue mark field dirty in detail view?

    now going back to post #1 you did say that.
    I just missed it.
    as long as it works well and good.
    thanks.
    thanks for reading

    gandhi

    version 11 3381 - 4096
    mysql backend
    http://www.alphawebprogramming.blogspot.com
    [email protected]
    Skype:[email protected]
    1 914 924 5171

    Comment


      #17
      Re: Does setValue mark field dirty in detail view?

      I think you want to use this in v12...

      {dialog.Object}.setValue(UXControlName,value [,honorChangeEvent] );

      markdirty.PNG
      Last edited by joegrun4; 05-13-2016, 03:13 AM.
      Alpha Anywhere V12.4.1 Build 3594-4665
      Application Server V12.4.1 Build 3594-4665 Running on Windows Server 2008 R2 Standard 4GB Ram X3430 @ 2.40GHz
      MySQL 5.5.38

      Comment


        #18
        Re: Does setValue mark field dirty in detail view?

        I have posed the question before without answer...WHY should any field be considered dirty at all with a submit button? Submit should just do as it implies and submit all of the information and there outta be 3 buttons - One called submit that actually submits all of the fields in the detail view, one that ONLY submits edited fields only and one that says submit nothing, then lets all sit back and watch which button gets used more!
        LOL.
        NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

        Comment


          #19
          Re: Does setValue mark field dirty in detail view?

          Well I would think the idea is for quicker data synchronization. Why have all fields push all data to the database if only one field has been changed?
          Alpha Anywhere V12.4.1 Build 3594-4665
          Application Server V12.4.1 Build 3594-4665 Running on Windows Server 2008 R2 Standard 4GB Ram X3430 @ 2.40GHz
          MySQL 5.5.38

          Comment


            #20
            Re: Does setValue mark field dirty in detail view?

            Agreed on the speed issue, but again how much speed would be lost over 3 fields submitting vs 35? My guess is that it would submit so quick either way. I can see the argument being made that in a multi-tenant application that you could potentially have thousands making edits and instead of a few edits now you have millions going on...so as I said I see your point in scalability.
            I just think there should be some sort of additional checkbox that say to always consider "dirty" that way we could test and set this up without error if there is an is dirty situation. Perhaps that is a BETTER solution than my 10 pound maul approach, lol.
            NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

            Comment


              #21
              Re: Does setValue mark field dirty in detail view?

              Originally posted by joegrun4 View Post
              I think you want to use this in v12...

              {dialog.Object}.setValue(UXControlName,value [,honorChangeEvent] );

              [ATTACH=CONFIG]42022[/ATTACH]
              I do use it, I BELIEVE I mentioned it in my OP (but I could be wrong). My point is that using SetValue (or, as I've just found out, modifying the field via a Lookup fill-in) does NOT set the field dirty so that, if you have the Detail View to update "Dirty Fields Only" then this information will NOT be saved.

              Comment


                #22
                Re: Does setValue mark field dirty in detail view?

                I'm not sure I understand your point completely (unless it's tongue-in-cheek and I'm just dense): The "Submit Nothing" is the close button, Submit can save dirty fields only or all fields depending on a setting in the Detail View's property pages. Granted, unless one can programmatically change that setting, you can't do it at run time with buttons.

                My point is simply that, if a field is NOT enabled, then regardless of whether its value is changed, it will NOT be updated in the backend (this is if you have the component set to update "Dirty Fields Only". As a result I need to use the "All Fields" setting. Dirty is dirty, it just appears that Alpha figures if a field is not enabled it CAN'T have its value changed.

                Comment


                  #23
                  Re: Does setValue mark field dirty in detail view?

                  http://wiki.alphasoftware.com/~alpha...ary.JS+Library

                  A5.form.setCtrlDirty(ele)

                  If a control is changed by user action, the event handlers created by A5.form.prepare() will set the control ?dirty? when the user leaves the control However, often a control value is changed by some other action, such as a Javascript action on the page, an action such as a lookup or date picker. If the list of ?dirty? controls is important for some action, every changed control must be set ?dirty? or it won?t be listed. If the user didn?t directly change the value, the ?dirty? attribute won?t be set. This function allows setting a control ?dirty?. If a control has an ID value of ?newdate?, this Javascript function call will set the ?a5isdirty? attribute to ?True?.

                  A5.form.setCtrlDirty('new date')

                  this question still was on my mind, and here is link for you to see. even though they do not specifically talk about hidden control or not.
                  i will see if i can run a test case again and post back if anything i find. ( i know last time it did not succeed)
                  thanks for reading

                  gandhi

                  version 11 3381 - 4096
                  mysql backend
                  http://www.alphawebprogramming.blogspot.com
                  [email protected]
                  Skype:[email protected]
                  1 914 924 5171

                  Comment


                    #24
                    Re: Does setValue mark field dirty in detail view?

                    gandhi:

                    Well, that answers my question, thank you very much.

                    Let me ask you a philosophical question: "If the documentation for a software feature is so buried that only someone like you can find it, does the feature actually exist"? In retrospect, someone may ask why I didn't immediately look at this page of the Wiki, but ex ante, at least IMO, it never occurred to me that the page even existed, let alone that I should look at it. That's where Alpha is at a disadvantage compared to something like Microsoft; Alpha's software, though in some ways remarkable, is so poorly documented that in order to use it effectively one requires a HUGE peer support group. The fact that the group here is so helpful despite being comparatively miniscule speaks to the knowledge and gracious nature of its members, but there are nevertheless limits.

                    BTW, most of my issues were with DISABLED, rather than hidden, fields, but I'm sure the information you linked pertains to the latter as well.

                    Comment

                    Working...
                    X