Page 1 of 1

Quote prices not appearing in the quote window

PostPosted: Tue Jan 06, 2026 4:04 pm
by JuiceyBrucey
Hi,
7.2.1.0
SR 16
I am putting through quotes and including the InventoryID, as well as the PartNo and UnitCost, but the prices are showing up as zero in JIWA quotes.
Here is an example of the payload item I am sending through:
'Lines' =>
array (
0 =>
(object) array(
'ItemNo' => 1,
'QuoteLineID' => '4ef2836c3c5042a8a9bd',
'InventoryID' => '4fe0f3a5ed9f4813a788',
'PartNo' => 'CHOOK2',
'Description' => 'PRO-VIT-MIN COMPLETE POULTRY MIX 20 KG',
'CommentLine' => false,
'QuantityOrdered' => 1.0,
'PriceExGst' => 0.0,
'PriceIncGst' => 0.0,
'DiscountedPrice' => 0.0,
'TaxToCharge' => 0.0,
'TaxRate' => 10.0,
'UnitCost' => 15.8,
'LineLinkID' => '',
'FixSellPrice' => false,
'UserDefinedFloat1' => 0.0,
'UserDefinedFloat2' => 0.0,
'UserDefinedFloat3' => 0.0,
'LineTotal' => 18.5,
'Weight' => 20.0,
'Cubic' => 0.0,
'DiscountedPercentage' => 0.0,
'DiscountGiven' => 0.0,
'QuantityDecimalPlaces' => 2,
'QuantityOriginalOrdered' => 1.0,
'NonInventory' => false,
'CustomFieldValues' =>
array (
),
'KitLineType' => 'e_SalesQuoteNormalLine',
'KitUnits' => 0.0,
),
Everything is working fine apart from the prices showing up in JIWA.
Is everything done correctly from my end?
Does JIWA determine price by what is sent by me, or does it cross check the price based on the InventoryID and the DebtorID?
Thank you.
Cheers

Re: Quote prices not appearing in the quote window  Topic is solved

PostPosted: Tue Jan 06, 2026 4:17 pm
by Mike.Sheen
Don't provide any prices and we'll work it out. The key one here is the DiscountedPrice.

You're providing 0.00 for the DiscountedPrice, and that's what we'll use. It's just as though the user keyed in ALL the values you've provided.

If you do not include the DiscountedPrice field in the DTO, then we'll follow the business rules and work out the price.

I'm assuming a lot here, because you don't mention how you are creating or updating the quote - you've not specified which route you are using, what REST verb and the payload you provided is not the Json payload, but a PHP representation - which I can understand, but courtesy would be to provide the actual representation of what is sent.

Re: Quote prices not appearing in the quote window

PostPosted: Tue Jan 06, 2026 4:36 pm
by JuiceyBrucey
Very sorry, sent you the reply that I get from JIWA, not the payload sent.
(This is a quote being created)
This is the items payload:
"Lines": [{
"ItemNo": 1,
"QuoteLineID": "na",
"InventoryID": "4c620d2e0c2e4ca6aaf5",
"Description": "ADVANCE ADULT ALL BREED CHICKEN CASSEROLE WET DOG FOOD 12X700 GR",
"QuantityOrdered": 1
},{
"ItemNo": 2,
"QuoteLineID": "na",
"InventoryID": "a6f8669405bb40308a13",
"Description": "ADVANCE ADULT ALL BREED CHICKEN CASSEROLE WET DOG FOOD 12X400 GR",
"QuantityOrdered": 1
},{
"ItemNo": 3,
"QuoteLineID": "na",
"InventoryID": "1283e8ef53a040c3a20e",
"Description": "ADVANCE DOG HEALTHY AGE LGE CHICKEN 15 KG",
"QuantityOrdered": 1
}]}

Originally it had prices in it, I removed all price information and sent through another quote, but price still not showing in JIWA.

Re: Quote prices not appearing in the quote window

PostPosted: Wed Jan 07, 2026 5:03 pm
by JuiceyBrucey
It seems to be working now.
Someone must have fixed it.
Thank you.
Cheers

Re: Quote prices not appearing in the quote window

PostPosted: Wed Jan 07, 2026 5:21 pm
by Mike.Sheen
JuiceyBrucey wrote:It seems to be working now.
Someone must have fixed it.
Thank you.
Cheers


If that is true, then you should adopt an approach of troubleshooting known as "known goods".

This means creating an environment without any customised plugins or anything else - a standard Jiwa demo database, with our standard REST API plugin and no other custom plugins.

It takes me 9 minutes to create a Windows VM, install Jiwa, create a demo database, configure and start the REST API and verify it is accepting requests.

Spend that 9 minutes and then test your operations against the "known goods" environment - if your problem still occurs, then that's actually good - because that's something we can readily verify and identify a work-around or solution - which means a fast result.

If your problem does not occur in this environment, then you can point the finger at something non-standard and start isolating what that is.

I can also guarantee your known goods environment won't suffer from mysterious fixes of unknown origin.