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

a5_report_excel_save - or passing arguments to json?

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

    a5_report_excel_save - or passing arguments to json?

    I've created a layout-table report based on an SQL query that I'd like to programmatically generate and save to an excel file. If you right-click the report and select "Show Xbasic...", the code is generated for various formats, including excel.

    The xbasic appears to run an undocumented xbasic function named a5_report_excel_save() that takes a single pointer variable 'def'. The pointer variable has several sub-elements including def.filter. I can set the def.filter element with no issue and the report runs fine.

    Unfortunately, the SQL table that I'm running the report against is quite large, and so I'd like to use arguments within the SQL query to filter on the SQL server rather than in the report itself. Adding arguments to the SQL query works fine, HOWEVER the "Specify Argument Values" dialog runs to set value at runtime, which won't work for my purpose- I need to run the report without user input.

    The problem is that I don't know where to programmatically set and pass the argument into the def pointer variable. There is a sub-element def.json that appears to be the logical place to look, but I just can't figure out where/how to pass it through.

    So I guess what I'm asking is:
    A) Is there any documentation for A5_report_excel_save()
    -or-
    B) does anyone know how to pass SQL arguments to either the def variable or the JSON statement?

    Here's the xbasic that is generated:

    Code:
    dim def as p
    dim def.filename as c ' optional filename
    dim def.filter as c ' optional filter
    dim def.excel as c = <<%str%
    '-- hundreds of lines of code to define the Excel report--
    %str%
    dim def.json as c = <<%json%
    { source : 'SQL:::Name::[MY-NAMED-CONNECTION]\nSELECT Statement_Date, Application, Account, Center, Acct_Type, Total_Debit_Trans, Qualifying_Debit_Trans  FROM dbo.[MY TABLE]  WHERE Month(Statement_Date) = Month(:LastDayOfMonth)  AND  Year(Statement_Date) = Year(:LastDayOfMonth)' , optimization : 'flat_order'  , calcs : '[ALL THE REPORT CALCULATIONS]'  , grand : {
     header : { '" [TITLE] "' : '" [TITLE] "' }
     , children : [
    { group_name : 'acct_type'  , break_expression : 'acct_type'  , order_expression : 'acct_type' 
     , header : { style_row_2 : '"font-underline:true;"' ,style_row_3 : '"font-underline:true;"' ,' [CALCULATED FIELD] ' : ' [CALCULATED FIELD] ' ,' [CALCULATED FIELD] ' : ' [CALCULATED FIELD] ' }
     ,children : [ { group_name : 'detail' 
     , footer : { statement_date : 'statement_date' ,account : 'account' ,center : 'center' ,total_debit_trans : 'total_debit_trans' ,qualifying_debit_trans : 'qualifying_debit_trans' }
     } ]
     }
     ]
     , footer : { 'System->Date' : 'System->Date' ,'system->pagexofy' : 'system->pagexofy' }
    }
    }
    
    %json%
    a5_report_excel_save(def)

    #2
    Re: a5_report_excel_save - or passing arguments to json?

    Answering my own question in case anyone finds it useful...

    I never found out anything further from A5_report_excel_save(), however, I did find how to use the Reporting Class in conjunction with the Show XBasic... > Convert to Excel code that is automatically generated to create nicely formatted reports that you can pass arguments into.

    1. Right-click your report, and select Show Xbasic...
    2. Choose the 'Convert to Excel' Tab
    3. Copy to clipboard

    You will only use the 2 text blocks from the generated code and discard the rest. Use the text blocks as shown in a new xbasic code page/block:
    Code:
    'declare and set the excel filename
    dim cFileName as c = "[COLOR="#B22222"]P:\My_Completed_Excel_Filename.xls[/COLOR]"
    
    'declare and set the arguments that you've built in the report
    dim args as sql::Arguments
    args.Set("MyArgument01","data")
    args.Set("MyArgument02","data")
    
    'declare and set excel template
    dim vExcelTemplate as Reporting::ReportExcelTemplate
    dim cExcel as c 
    cExcel =<<%str% 
    ...[COLOR="#0000FF"]Paste the %str% code block from the def.excel [/COLOR]...
    %str%
    
    vExcelTemplate.FromString(cExcel)
    
    'declare and set the json
    dim cJSON as c
    cJSON = <<%json%
    ...[COLOR="#0000FF"]Paste the %json% code block from the def.json [/COLOR]...
    %json%
    
    'use the Reporting Class to generate the report
    dim rg as Reporting::ReportDataGenerate
    rg.Source = "Database:[PathAlias.ADB_Path]\[COLOR="#B22222"]My_ALB_Filename[/COLOR].alb"
    rg.Populate(cJSON)
    rg.Arguments = args
    rg.ExcelTemplate = vExcelTemplate
    rg.GenerateExcel(cFileName)

    Comment

    Working...
    X