Can't get Inventory Import Debtor Specific Prices to work

[DannyC]

The plugin Inventory Import Debtor Specific Prices I can't get to work.
I've attached the file I am using.

I just want to add a debtor to an existing PartNo.
And I also want to be able to edit an existing debtor specific pricing.

In the Inventory Import screen, I am setting the appropriate destination Property, if I tick "Update existing inventory" it says succeeded but no extra DSP row has been added. If I don't tick Update Existing Inventory I get an error PartNo 1140008 is already in use.

Is there some hidden magic to get it to work?

Version 7.2.1 latest SR.

[Mike.Sheen]

Using your file, I can see the first clue immediately:

InventoryImport.png (37.65 KiB) Viewed 584 times

The Debtor column in your file is not mapped. You need to change that, or use column names matching that shown in the plugin description:

Sample File:

DebtorSpecificPriceRecID, PartNo, DebtorAccountNo, Source, Mode, Amount, UseQuantityBreak, Debtor Quantity Break
, 1170, 1001, sellprice, Percentage, -5.25, true, 5
, 1170, 1001, lastcost, Percentage, 8.50, true, 6
78E5AD93EDC84A1DBF7A, 1171, 1001, rrp, Percentage, -10.00, true, 10
, 1171, 1001, p1, Percentage, -10.00, true, 15
, 1172, 1001, p1, None, 112.25, true, 20

Your file has these columns:

PartNo,Debtor,Source,OPMOde,Amount,UseQtyBreak,QtyBreak
1140008,1001,SellPrice,percentage,-6,false,0

Which isn't wrong - it just means you need to manually select the Destination Property in the mappings grid. But if you want to have those mappings done automatically, you need to have the column match one of the aliases defined by the plugin. The aliases can be seen in the code - for example the debtor account no. column has multiple aliases which will result in it being auto-mapped for you:

And BTW the part 1140008 which is in your file doesn't exist in demo data - but 01140008 does.

[DannyC]

it just means you need to manually select the Destination Property in the mappings grid

Which I am doing.

But I am embarrassed to admit...it was that flippin' leading zero on the PartNo!

[Mike.Sheen]

But I am embarrassed to admit...it was that flippin' leading zero on the PartNo!

How? The message you were getting was " it says succeeded but no extra DSP row has been added" - the leading 0 should have gotten you an error about part '1140008' not being found.

[DannyC]

Nah, error was PartNo 1140008 is already in use.
And in my idiocy, I realise I had both 01140008 and 1140008 as parts.

And all the testing I had done with item 1140008 which showed as succeeded actually had in fact succeeded. I was only looking at 01140008 not realising I had a partno 1140008.

Anyway it works - to add new lines to debtor specific price.
If the debtor exists, it still adds a new line rather than updating what is already there.

[SBarnes]

Although this is not related it bears mentioning given this is about pricing, if the data is manipulated in excel first and then exported to csv and you have any formatting turned on on any of the columns say like money for the rrp, excel will insert the $ sign into the text and Jiwa does not take well to it.

In other words if in terms of the database a field is a number, the import file must be a number and nothing else for that column, so turning off any column formatting in excel is a good idea.

[Mike.Sheen]

I realise I had both 01140008 and 1140008 as parts.

And all the testing I had done with item 1140008 which showed as succeeded actually had in fact succeeded. I was only looking at 01140008 not realising I had a partno 1140008.

I have days like that sometimes.

[SBarnes]

Your part number example is where Excel formatting would also bring you undone as excel will strip the leading zero if it thinks the column is numbers and not text.