you need to 'escape' the quotes around "available" by putting a backslash in front of them.  Try the example below.  I added the \ before the quotes, and also added a second inventory quantity so that you can see how the additional quantities can be requested.

{"query":"query { inventoryItem ( id: \"gid://shopify/InventoryItem/41450849599575\") { id inventoryLevels(first:2) { edges { node { id location { id name } quantities(names: [\"available\",\"on_hand\"]) { name quantity } } } } } }" }

This week, we had an error #117 show up in one of our files that processes thousands of records in and out on any given day. We were able to recover what looks like all of the data in the file using the PxPlus utility.
Are there any insights as to why this would show up?

I'm having a lot of trouble with the 'quantities' field in the InventoryItem section to work. For example, the following works fine:

{ "query": "query { inventoryItem(id:\"gid://shopify/InventoryItem/41450849599575\") { id inventoryLevels(first:2) { edges { node { id location { id name } } } } } }" }

However, if I insert the quantities logic:

{ "query": "query { inventoryItem(id:\"gid://shopify/InventoryItem/41450849599575\") { id inventoryLevels(first:2) { edges { node { id location { id name } quantities(names: ["available"]) { name quantity } } } } } }" }

The response from the query is 'Bad Request'.

I've taken this logic from numerous examples I've found, and I've no clue as to why it doesn't work.

Any ideas would be welcome.

Ok.  I was able to access the design view for the table in question *and* the one that worked.  The one failing had a lookup defined.  When I had the Access developer remove that lookup I was able to get a good open.  Thought others might like to know.

It should be possible.

If you can install Windows you should be able to run PxPlus.

Now I think it is running a arm version of Windows so PxPlus would be running via Windows x86 emulation so may not run as fast as if it was running natively on a x86 machine. Although the hardware is fast itself so that may more then make up for it.

I have an Access DSN (user, I would love to know if anyone has successfully set up an Access System DSN).  This open works:

0220 open (hfn,iol=*,err=9010)"[ODB]TearDownLive;ReceiptTable;key=CoreItemCheckDigit"; in=lfo

But this throws an error 80 - Invalid key definition, number or name.

0220 open (hfn,iol=*,err=9010)"[ODB]TearDownLive;OutInventTable;key=CoreItemCheckDigit"; in=lfo

The person who developed the access tables says they are the same.  Any insight here would be appreciated.  This was supposed to be the easy part .

Hi,

Is it possible to run pxplus using Windows in parallels with the Apple M chip?

Regards,
HendersonS

How can I translate this Excel macro to PxPlus?

function main(workbook: ExcelScript.Workbook) {
let sheet1 = workbook.getWorksheet("sheet1");
// Add a new table at range A1:L10 on sheet1
let newTable = workbook.addTable(sheet1.getRange("A1:L10"), true);
}


I tried to add the parameter programmatically.  It is not displaying in the parameter list

LET REPORTNAME$="C:\PXPLUS\ABCdef.pvr"

00130 LET RPT=NEW("*rpt/pvxreport"); IF RPT=0 THEN END
00131 LET RPT$=STR(RPT)
00132 IF RPT'OPEN(REPORTNAME$)=0 THEN MSGBOX "Could not open report file:"+SEP+SEP+MSG(ERR)+SEP+MSG(-1),"Initialization error","!"


00261 RPT'CLEARPARAMS()
00270 LET P=RPT'ADDPARAM()
00280 LET P'NAME$="COMPANY"
00290 LET P'DESCRIPTION$="COMPANY NAME"
00300 LET P'TYPE$="S"
00310 LET P'LENGTH=30
00320 LET P'VALUE$="ABC & CO"



I tried with above code.   After this when i looked into the definition it does not show the new parameter in the parameters list.


Method 2
========

Alternatively i saved the above code ( from 261 to 320) in a separate program and stored it in REPORT_OPTIONS--->CUSTOM_INTERFACES--->PARAMETER_INTERFACES---->PROGRAM

It is not working.

"ANY EXAMPLE/CODING  TO ADD PARAMTER PROGRAMATICALLY

SURIAKUMAR