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

(dialog.object.newRecord(cloneExisting... Used at part of UX to add records not working

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

  • (dialog.object.newRecord(cloneExisting... Used at part of UX to add records not working

    All,

    I have a UX that I want to use to add new records to the database.
    I want the new record to retain information in some of the fields from the existing record and present others as blanks to enter data in.
    The UX contains a list and many fields databound to the underlying table all of that works well.

    The method
    {dialog.object}.newRecord({cloneExisting: flagClone, fieldsToNotCopy: ignoreList});
    seems to be designed to do just what I want. However for me it is not working.

    I put this in the onClick event of a button, with flagClone = true and an appropriate list of fields as shown below:
    {dialog.object}.newRecord({cloneExisting: true, fieldsToNotCopy: ['GBSF','F_I_P_R','ITEM_DATE','TASK_CODE_NO']});

    After saving and going to Working Preview, clicking on the button will work one time, allowing me to add one record.
    after submitting that one record, it will not work again, in fact the button does nothing at that point.
    There is no change to the input screen and nothing gets "dirty"

    I have used the base form of this method {dialog.object}.newRecord(); and that works for adding multiple records in sequence as expected.
    I am running AlphaAnywhere V12, Build 2999 System addins 4519, I applied patches today.
    Windows 10

    I will be happy to share screen shots etc.. just tell me what you wish to see.

    A few questions:
    1) Am i missing something here?
    2) Are the field names case sensitive, All my fields are all lowercase with no spaces, I've tried both upper and lower case field names with the same bad result.

    Thanks for the help

    Kevin

  • #2
    Re: (dialog.object.newRecord(cloneExisting... Used at part of UX to add records not working

    Hi Kevin,

    I just tried this and it seems ok. Fieldnames seems to be case-insensitive. When you say... "Build 2999... I applied patches today"... what does that mean. That you patched up to 2999... or you're running a pre-release?
    The only suggestion I have is post your UX and a table (with a few records) and I'll have a look.

    Comment


    • #3
      Re: (dialog.object.newRecord(cloneExisting... Used at part of UX to add records not working

      David
      Thanks for the reply. I am not running any pre-release version.
      I forgot to mention, I am using a MYSQL database
      I've attached the UX, I'm not sure how to attach a table and there are several that this UX references (mostly as lookups for dropdown menus)
      I do have my development site on Zebrahost and would give you the password privately if you wanted to poke around there.


      You will see in the attached UX three buttons for adding records, the top one works, the bottom two work once, then stop.

      Kevin
      Attached Files
      Last edited by Kevin at LECESSE; 03-18-2016, 02:27 PM. Reason: Attached Wrong Version of UX file

      Comment


      • #4
        Re: (dialog.object.newRecord(cloneExisting... In UX: PROBLEM SOLVED

        All,

        I was trying create a UX with an embedded list to add a new records which retained some of the values from the previous record to avoid typing repeating information over again. Cloning a partial record.

        This was a case of inexperienced operator error. (inexperience with JavaScript and all the things it can do)
        My UX didn't work correctly because there was a stray Javascript Action that was populating all my controls, after the {Dialog.Oject.newRecord({cloneExisting: true, fieldsToNot Copy: ['field_1','field_2','field_3"]}); method fired. Once I got rid of that, things worked as expected.

        Here is where I have Action Javascript related to this task
        LOCATION: UX: Properties: Javascript: Javascript Actions - ACTION: Populate Controls in a UX component with data from Tables

        LOCATION: UX: Controls: Add New record Button: Javascript - (touch, mouse...: Click - ACTION: {Dialog.Object}.newRecord({cloneExisting: true, fieldsToNotCopy: ['Primary_key_field','field_1',field_2','field_3','as_many_additional_fields_as_needed']});

        You need to have all the {, [, (, ' and ,'s in the correct places

        LOCATION: UX: Events: Server-side: ACTION: ExecuteServerSideAction("Save Data::Save_Submitted_Data_to_Table_s_2")

        There is pretty good documentation on the first and third of the items above in the Liberty Manuals

        Also note, I included the auto increment field for the table in the list of fieldsToNotCopy so I would avoid creating a new record with the same primary key field value.
        I'm not sure that is required.


        Thanks to DavidK for commenting.


        Kevin Callanan

        Comment

        Working...
        X