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

UX LIST control Custom Data Source xBasic called by Alpha at design time fails.

  • Filter
  • Time
  • Show
Clear All
new posts

    UX LIST control Custom Data Source xBasic called by Alpha at design time fails.

    Can someone tell me the proper way to code an XBasic function specifically for the source of a LIST control on a UX?

    I have looked at the three on-screen sample snippets and none of them address the issue I am having:

    The Alpha UX Designer insists on calling the xBasic function to get a list of fields that will be used and since session variables and/or UX arguments have not been initialized, the code fails.

    What is the recommended way of knowing when the function is being called simply to get a list of data fields for the designer?

    Re: UX LIST control Custom Data Source xBasic called by Alpha at design time fails.

    Execute a simpler version of your XBasic List code in order to design your List. Since you're using session vars / arguments in your sql execute statement, then set those arguments locally... while designing your List. Your first goal is to get an XBasic function to return rows, formatted for the List. Then you can start setting up incoming variables and arguments which will exist before your List gets rendered.

    So, while testing and setting up, initialize everything you need in the XBasic List code.


      Re: UX LIST control Custom Data Source xBasic called by Alpha at design time fails.

      David, my problem came up well after my UX and LIST had been developed and moved into production. So, putting in a simpler version of the code just to do a little bit of debugging was something I did not want to do, if it could be avoided. My UX was working perfectly with my development database and with my testing data on the production server. But it would not work outside of those two systems.

      The solution I reluctantly adopted was to supply default values for all of the Arguments in the UX. Default values keep the Alpha LIST designer happy because it can retrieve sample data whenever it wants.

      Maybe Alpha assumes developers will supply default values when defining Arguments. But, I have been very reluctant to do this because I have been afraid those default values might end up getting used by Alpha in a production environment. It would be really bad if my development default values appeared in a production system. The user could end up seeing data that made absolutely no sense, or worse yet, in this multi-tenant app, they might see some other tenant's data!

      The problem that prompted this post in this first place turned out to be an issue where Alpha was using a primary key value from my testing database and not the intended primary key value from the production database! This was not because of Arguments, but I think the point is the same - for some inexplicable reason a value that I had used during testing got persisted into the component for production! I never found where this value was coming from in the UX Designer. However, I did see a line of code near the very bottom of XBasic source of the component that was declaring my problem variable:

      DIM tmpl.rtc.cpModel_SysID as C = "2"

      I had XBasic code to declare and then initialize the variable in two separate lines of code in a server-side event which I had hoped would make the variable available to a custom field in the LIST. I had thought my initialize code was working, but it hadn't been. No matter what, this variable always had a value of "2" when I went to use it. I didn't discover this until I tried to run the system outside of my two testing databases.


        Re: UX LIST control Custom Data Source xBasic called by Alpha at design time fails.

        I don't like to supply default values either... handy at times... but risky.

        For the XBasic List function, I would just hard code whatever variables I need for testing... that's all... that's what I meant by a simpler version. Allow the XBasic code to work on it's own, running in Live or Working Preview for debugging. Hard code the session vars which can then simply be commented out when testing moves to the List. There's no other way to test the XBasic by itself.


          Re: UX LIST control Custom Data Source xBasic called by Alpha at design time fails.

          I always used a copy of the latest component to make the changes (kept it away from live) - it was painful but pasting in the temporary values is the only way I could figure out to use it as well - it's a difficult problem.
          Insanity: doing the same thing over and over again and expecting different results.
          Albert Einstein, (attributed)
          US (German-born) physicist (1879 - 1955)


            Re: UX LIST control Custom Data Source xBasic called by Alpha at design time fails.

            I think it would be nice if the "e.getDataMode" variable that gets passed into the custom Xbasic source procedure for populating a list had at least one more value, like "getColNames" that the designer (or even the server for that matter) would use when it needed a list of column names. I suppose Alpha may want sample data or data types, if so maybe it could pass in a different value like, "getSampleData".

            There may also be one other complication: the use of "Custom Control" fields in a LIST. My LIST uses two Custom Control fields and one of those needs a value that happens to remain constant for the given set of records that are being displayed by the LIST. That semi-constant piece of data is not very convenient or practical to gather from SQL and place into all the records in the LIST.


              Re: UX LIST control Custom Data Source xBasic called by Alpha at design time fails.

              Have to disagree. It's a process of developments step just like anything else. If a component is expecting data from XBasic, you build and test the XBasic process on it's own first... always. Otherwise, you never know which piece is not working. Once the function is working independently, you work it into the List. Also, I wouldn't think adding a constant into the SQL data would be a big deal. It's all tough because it's all new to you... but this is advanced stuff... so... it takes a bit of time to become familiar with it.