Issue when moving from Development to Alpha Application Server

[aprescott]

I am in the process of publishing my first ever web app, and while it seemed to go pretty smoothly, I'm seeing an issue on my main component (a UX with panels and lists).

The component runs completely as desired in Working and Live Preview, but once I publish it to a LAN server using Alpha Application Server (Build 7544-5564) the issue arises.

The issue:

UX component (opened in a Tabbed UI) displaying a single record/fields on left hand side, on right hand side is a panel with a list component that uses argument ID to filter the list. (ID_number = :ID, where :ID is set at runtime using the value in the ID_Number field). What is happening is that no data appears to be loading. the panel header and column names for the list render perfectly fine, but nothing below. I'm not certain if it is timing out (though I did try setting the list to Select only the first 10 records to reduce the amount of time, to no avail) or if there is some other issue. Again, all of this works as desired in Live Preview, and even when I do a preview in the browser.

Any thoughts on how I can troubleshoot this? I am still new to web app building, so I might be missing an obvious answer.

Thanks in advance!

Edited to add: I have other components in this app that filter a list control in a similar fashion (using arguments) and they seem to work fine.

[mikeallenbrown]

Maybe the connection string needs to be edited so that it can connect to your data source from the LAN?

[aprescott]

I think connection string is good (I did adjust it to the new location) as other data is pulled, just not the list on the UX.

[peteconway]

If you turn of the argument in the list and have it display all, does the list populate?

[aprescott]

peteconway , yes - turning off the argument filter in the list populates the list. The list also populates if I set the filter to a static value (i.e., ID_number = 504). I figured there was some issue with the argument but not sure how else to do it.

[scrimej]

Did you set the 2nd list to have a parent list and make the association to the first list?

[peteconway]

So the arg value isn't there

using the js on the client side check the value in the argument is set e.g. var av = {dialog.Object}.argumentValue('ID'); alert('this is the value of the ID arg.." + av); when you select the record. There are several things that can do this, is the arg a Number or a Char etc. is the List onClick returning the value you want (expect) or some other value - you need to confirm what value is being passed to the argument from the List - when you see that is what you expect - it will be a timing issue. Note - I never use or liked the Tabbed UI - good luck.


Pete

[aprescott]

Using the code you suggested in onRenderComplete, and the alert says the argument value is 0, so I'm guessing the argument is not getting passed. Again, the alert has the correct ID number when I try it in Live PReview

one note, the argument value isn't coming from a list, but rather a control that was populated using ExecuteServerSideAction("Populate Dialog from Tables"). Then the argument is passed into a list.

[peteconway]

You need to turn that off in my view - bind the list to the controls using detail view - make certain the SQL data source is returning the primary Key and then it will work.

There are lots of things in AA you don't need these days and I think ExecuteServerSideAction("Populate Dialog from Tables") is on that list.

[peteconway]

2021-07-15_16-45-05.png

[aprescott]

Looks like it was a timing issue. I found that if I made a button to refresh list data after the page renders, everything worked well. So I just added a javascript to automatically refresh the list data after populating and everything is loading as it should. Weird that it worked the old way before going to Application Server, though.

Thank you for your time, advice, and help!

[peteconway]

Cheers
Pete