I've got a form with a lot of entry fields that I've assigned as parameters to a modify fex that runs via the save button onclick. When I test by clicking my save button, I find that not all of the entered fields end up making it over to that fex. Is there a limit in the number of parameters that can be passed, the number of bytes of data that can be passed via parameters, or some other limit that I'm not aware of (with recommended workarounds)?

Also, I'm curious if when calling a fex with Modify, you can suppress the popup window with the standard modify result display, and instead, use the return code results to display a custom message in the calling form. We're on 5.3.4 now going to 7.1.4 soon.

TGT,

The standard method of HTML form execution is POST and this restricts the length of your URL string to about 2044 bytes (not quite 2K) and this is often the problem with parameters not being completely passed to the executed program. You can change the method to GET and this extends the permissible length well beyond what you would probably require (I've never managed to exceed it).

However, there is always a downside and the differing methods are no exception. POST will hide the parameter string in the address of the browser so you will get something like "http://[servername]/ibi_apps/WFServlet" whereas with GET you will see the entire URL sent by the form including all the variables and values.

This can sometimes be an advantage though, because if you have a table of data in HTML format (e.g. NOT Excel) you can right click and then export to MS Excel from the report itself without having to rerun your request (see the excellent FOCUS on Developers Article by Urszula Politowicz and Susannah Jones of Elie Tahari).

The main distinction between these two methods however, is that GET is generally used for retrieving data and POST - you've guessed it - is for sending data outwards for programmatical updates to databases.

Hope this helps

T