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

Getting Viewbox data to use in UX

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

    Getting Viewbox data to use in UX

    I'm attempting to extract the data from the viewbox and use it on the component level. There's other threads on how to do this and I've successfully done it with one of the header values. But how would you extract the javascript calculated field, 'totalExtendedPrice' in the viewbox to go into the 'Total' field on the UX?

    The attached extracts the CustomerID but I can't figure out how to get the totalExtendedPrice value to that field.

    testUX.zip

    #2
    Re: Getting Viewbox data to use in UX

    Update:

    I've figured out how to pull the line item total. Now I need to pull the summary of these subtotals.

    Code:
    function getSubTotal() {
    
    var vb = {dialog.object}.getControl('viewbox1');
    
    	var qty = vb.data[0].orders[0].orderItems[0].Quantity;
    	var price = vb.data[0].orders[0].orderItems[0].UnitPrice;
    	var subtotal = qty * price
    	
    	{dialog.object}.setValue('Total',subtotal);
    
    }
    This is using the sample data in a viewbox.

    Comment


      #3
      Re: Getting Viewbox data to use in UX

      Code:
      function getSubTotal() {
      function getSubTotal() {
         var vb = {dialog.object}.getControl('viewbox1');
         var grandTotal = 0;
         var customerTotal = 0;
         var orderTotal = 0;
      
         var qty = 0;
         var price = 0;
         var extended = 0;
       
         for( i=0; i < vb.data.length; i++  ) {
            customerTotal = 0;
      	   for( j=0; j < vb.data[i].orders.length; j++ ) {
      	      orderTotal = 0;
      	      for( k=0; k < vb.data[i].orders[j].orderItems.length; k++ ) {        
      	         qty = Number(vb.data[i].orders[j].orderItems[k].Quantity);  // just incase AA isn't really storing it as a number field
      	         price = Number(vb.data[i].orders[j].orderItems[k].UnitPrice);
      	         extended = qty * price;
      	         orderTotal = orderTotal + extended;
      	         customerTotal = customerTotal + extended;
      	         grandTotal = grandTotal + extended;
      	      }
      	   }
      	  {dialog.object}.setValue('Total',customerTotal);  // for a customer total
      	}
      // ?  {dialog.object}.setValue('Total',grandTotal);  // for a grand total
      }
      }
      Last edited by RichCPT; 11-18-2017, 05:31 PM. Reason: Added 3rd loop and replaced [0] with [i], [j], or [k]

      Comment


        #4
        Re: Getting Viewbox data to use in UX

        If the object of the exercise is to get the example Grand Total value of $4,596.20, then you're logic is off. With your code against the sample data I got $4,101. The loop logic should be...

        Code:
           for( j=0; j < vb.data[0].orders.length; j++ ) {
              orderTotal = 0;
              for( k=0; k < vb.data[0].orders[j].orderItems.length; k++ ) {        
                 qty = Number(vb.data[0].orders[j].orderItems[k].Quantity);  // just incase AA isn't really storing it as a number field
                 price = Number(vb.data[0].orders[j].orderItems[k].UnitPrice);
                 extended = extended + (qty * price);
              }
           }
        
         {dialog.object}.setValue('Total',extended);  // for grand total
        I'm not sure that's what David is going after... it isn't that clear.

        You could also shove a <span> tag into the ViewBox layout and grab the total that way...

        Code:
        Grand total: <b><span id="myTotal">{[temp].grandTotal:number('$#,###.00')}</span></b>
        I wouldn't be surprised if there an internal Alpha way to get that calculated data... but I can't find any doc on it.

        Comment


          #5
          Re: Getting Viewbox data to use in UX

          David, yes. That's the total I was looking for. I'm using this in place of a repeating section inside a repeating section because I can pull all the data and display it from multiple tables, then total it, then pass the total to the base UX component to be saved in the main table.

          Kinda confusing, but it makes sense to me I guess. I'm just displaying 1 order and pulling that total. But this gives me options for other things that I can do.

          Thank you both!

          Comment


            #6
            Re: Getting Viewbox data to use in UX

            David, yeah thanks. I just realized that, too. I had not replaced the [0] indexes with the appropriate j or k index. I also edited the code in post # 3 to include three loops instead of two, since we don't know for sure if there is just one customer in the data. I has also thought about suggesting adding an ID to the html element (like in your post 4) that holds the "grand" (not sure if this is total for one customer or total across all customers in the data) total and also including a row number, customer ID and/or order ID, to make the ID unique, incase the data and template generated more than one "grand" total line.

            Comment

            Working...
            X