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

JSON Parsing Question on a UX Dialog

  • Filter
  • Time
  • Show
Clear All
new posts

    JSON Parsing Question on a UX Dialog

    I have this data being returned from an API.

    "code": "829576019311",
      "codeType": "UPC",
      "product": {
        "name": "Goodfellow and Co No. 01 Blue Sage Tonka Texturizing Fiber, 4 Oz.",
        "description": "No. 01 Blue Sage and Tonka Texturizing Fiber from Goodfellow and Co gives you...",
        "imageUrl": "images/54066938.jpeg",
        "brand": "Goodfellow and Co",
        "specs": [
            ["Item Form", "Clay"],
            ["Liquid Volume", "4 Fluid Ounces"],
            ["Scent", "Lime, Amber"]
      "category": "Hair Care"
    I've got all the javascript done parsing this and putting it into fields on a UX Dialog. The product.specs data is currently all going into a TextArea component called 'specs' using

    The question is, those specs vary from product to product, and the number of them vary as well. What type of component would I use to insert them into? A Repeating Section maybe? I'm taking this data and letting the user decide whether to insert into their SQL database.​

    Have you considered putting them in a viewbox ?
    Gregg is a great site to test and share sql code


      i feel like we should all be looking at these "viewboxes" they seem to be pretty awesome from all the chatter
      NWCOPRO: Nuisance Wildlife Control Software My Application: "Without forgetting, we would have no memory at what was I saying?"


        Originally posted by CharlesParker View Post
        i feel like we should all be looking at these "viewboxes" they seem to be pretty awesome from all the chatter
        Me too. I've made a small effort but just haven't committed myself fully.
        Mike Brown - Contact Me
        Programmatic Technologies, LLC
        Independent Developer & Consultant​​


          I am in same camp. I know I need to go there and have only procrastinated because I can currently be very productive with the tools I know (ux list).

          Pete Conway keeps me plugged in a bit with his progress and it’s on another level of speed and what’s possible… which motivates me to start making the plunge.


            I use viewboxes all over the place. Lightweight. I thought about this one as well. Got sidetracked with another part of the project.


              The JSON Form has lots of promise for use with viewboxes.
              I am working on a project now that will let you update the data in the viewbox using the JSON Form,
              add new records using the same JSON Form (adding it to the viewbox before making the callback to sql),
              and then finally write the changes and inserts with one push of the button.

              The issue I'm running into is my desire to display/change the buttons depending on the values of certain stateInfo[] variables.
              I'm aware the javascript expression shown in the image below is always false, but that's only because I want to confirm the button would
              be hidden if the expression was false.

              IF anyone knows of a way to use stateInfo[] variables in these javascript expressions, that information would be greatly appreciated.
              If not, I will end up hiding text controls outside of viewbox and JSON Form to get things to work.
              I think the difference between the two is only a few lines of code, but I'd prefer to use less code if possible.

     is a great site to test and share sql code


                Hi Gregg,

                Good to see you are working with jsonForms, lots of javascript involved to get them working and xbasic to save the data but worth it I think.

                This code works for show/hide of a button, I set the stateInfo of myvar1 to the value of the row number in a viewbox with {dialog.object}.setStateInfo({myvar1:v}); on the onclick item for a row and then in the show/hide I put
                var stateInfo = {dialog.object}.stateInfo;
                var myvar1 = stateInfo["myvar1"];
                    return true;
                    return false;


                  Nice to see you active again. I use the viewbox on-click to populate the JSON Form. Then the update button to put changes into the viewbox and populate a stateInfo variable
                  with objects waiting to be committed to the backend. I didn't realize we could actually put that much code into the show/hide expression.
         is a great site to test and share sql code


                    The Viewbox should have it own forum as its a totally different approach to all the other controls and can replace almost all of them as well and be 90-99% lighter and faster.
                    Insanity: doing the same thing over and over again and expecting different results.
                    Albert Einstein, (attributed)
                    US (German-born) physicist (1879 - 1955)