URL parameter not in payload

Wappler General Need Help
1

Hey guys,

I’m facing a problem that I haven’t seen before and it would be very handy if anybody has an advice/idea…

I have a few query params set in my page and they are sent as input to my serverAction and filter a query results…
-Win 10
-php , MySQL
-wappler v6.0.0 beta 8 , STABLE

One query parameter prcto is not sent to server-side (not in payload)… I cannot understand why…

image
image1920×1029 175 KB

I have checked:

  1. All the parameters are set and present in my url
  2. The param “prcto” is normally setup in my config.js under my pageApp node

Anybody has any idea where to search? How to solve it?

2

Are you sure its value (query.prcto) is used anywhere on your page? How do you call the order_list server action - please post its code here.

3

At the moment I use GET… I was going to change it to POST as soon as I will check that everything works well
Anyway here is me Query Manager

image
image452×1069 22 KB

And here is the code of setting it up:

<div class="d-flex col-12 justify-content-center align-items-baseline px-2 py-1 bg-secondary bg-opacity-25">
     <button id="btn_setPrcRng" class="btn btn-danger btn-sm lh-sm w-100 shadow-sm" dmx-show="rng_changed.value==1" dmx-on:click="queryMngOrders.set('prcfrm',prcRangeFrom.value.toNumber());queryMngOrders.set('prcto',prcRangeTo.value.toNumber());rng_changed.setValue(0)">Submit Price range</button>
</div>
4

I am not sure i understand what you mean. POST params are only used when submitting a form. GET params are available when calling the server action from the page.
Also - i don’t understand why did you post the button code i asked you for the server connect code from your page.

5 
<dmx-serverconnect id="srvc_OrderList" url="dmxConnect/api/admin/orders/crud/order_list.php" dmx-param:sort="queryMngOrders.data.sort" dmx-param:dir="queryMngOrders.data.dir" dmx-param:offset="queryMngOrders.data.offset" dmx-param:limit="queryMngOrders.data.limit" dmx-param:catid="queryMngOrders.data.catid" dmx-param:grpid="queryMngOrders.data.grpid" dmx-param:prdid="queryMngOrders.data.prdid" dmx-param:varid="queryMngOrders.data.varid" dmx-param:varoptid="queryMngOrders.data.varoptid" dmx-param:clntid="queryMngOrders.data.clntid" dmx-param:agntid="queryMngOrders.data.agntid" dmx-param:delivfrm="queryMngOrders.data.delivfrm" dmx-param:delivto="queryMngOrders.data.delivto" dmx-param:fltr="queryMngOrders.data.fltr" dmx-param:dltd="queryMngOrders.data.dltd?queryMngOrders.data.dltd:0" dmx-param:sent="queryMngOrders.data.sent" dmx-param:stats="queryMngOrders.data.stats" dmx-param:prcto="queryMngOrders.data.prvto" dmx-param:prcfrm="queryMngOrders.data.prcfrm" dmx-param:datefrm="queryMngOrders.data.datefrm" dmx-param:dateto="queryMngOrders.data.dateto"></dmx-serverconnect>
6

Sorry, Got it brother…
You are right

prvto is not the same with prcto

7

Yes indeed, the value used there is wrong.

1 Like
8

Thanks!! As I say… “Machines and Code can’t be wrong… Just the data you provide them can be wrong” :beer: