× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



That is what I thought I was achieving _by_ selecting the Detect Length option Anshul. Guess I had it back to front.

It just tried redeploying and deselected the detect length but no other options appear and PRODUCTLIST_LENGTH still appears in the output.

Can you tell me what the name of the box I'm looking for is and on what screen it appears.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jul 15, 2019, at 9:00 PM, anshul narang <narang.anshul@xxxxxxxxx> wrote:

Hi Jon

Can you post the code ? So there are two aspects to it . Lets say you have
datastructure with dim 20 . In your code you are only populating the 3
rows.
If you put datastructure in output then you will get 6 rows with data and
14 would have structure but no values in the datastructure field.

So to avoid that issue of populating blank values . We use the concept
Nadir/Martin pointed out in which we will have two output prams length and
datastructure . When you are deploying yhe webservices , please uncheck the
detect field length. Then you will have option with length of 20 and in
drop down you can use length for dim.a

Benefit of using it is you will have now 3 rows not 20 and you will have
one more output called length,

{
"XXX_DS": [
{ first datastructure row },
{ second datastructure row},
{third datastructure row } ]
"length":3 }

Without Length concept

{
"XXX_DS": [
{ first data structure row },
{ second datastructure row},
{third datastructure row }
.
.
{ 20th datastructure row}

}

Hope it makes sense!
I am just trying to help as I have also struggled in past with these issues.

Thanks
Anshul



On Mon, Jul 15, 2019 at 8:29 PM Booth Martin <booth@xxxxxxxxxxxx> wrote:

One other thought occurs to me... Are you expecting productList to be
truncated to the length of _LENGTH?

The productList will have 20 elements, always. The only function of
the _lENGTH parm is as information for who ever is consuming the data,
so that they will know how many elements to look for. No changes in
productList take place because of the _LENGTH parm.


On 7/15/2019 7:11 PM, Booth Martin wrote:
I am not sure what you mean by "ignoring it"?
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.