[n.tiwari@manduka.com]

We have created Inventory Reports for Europe and we wanted to include the list Prices for Wholesale and Direct Price Levels for all your items in this report.

I contacted NetSuite support and they mentioned that the ability to add Base Price in multiple currency in Inventory Reports is still an Enhancement and is currently logged under Issue 137377.

Now, I asked them if we can source the base price on a custom field instead – e.g. EU List Price Direct and EU List Price Wholesale – two custom fields for two of the price levels that are used for EU reports.

They haven’t got back to me yet so I wanted to reach out the forum community here if we can handle this issue in a better way.

Creation of custom fields should be the last option. If you think there is a better way to include the base price for Direct and Wholesale in the EU report, please do let me know.
This is a cached copy. Click here to see the original post.

[n.tiwari@manduka.com]

Actually, I am now able to add a EU Direct price custom field which sources its value from an Item Search. I have confirmed on multiple Inventory Items that the value is being pulled correctly.

Now, my only challenge remaining is to put this new custom field in a report as one of the columns. I do not find the new custom field in the report as one of the fields when I do a search. Does anyone know how do I make a custom field appear in the report? The custom field does not store value as it sources its value from a search.

[erictgrubaugh]

If `Store Value` is unchecked in your Custom Field definition, which you may need for Sourcing to behave properly, then I’m not sure that it will show up in the Reporting columns.

[n.tiwari@manduka.com]

erictgrubaugh – I posted this question in the slack community and got a response for using a saved search instead of a report to display the unit price. I did that and trying to get feedback from my colleague and see how it goes.

I did thought of an alternate, dirty solution – to use two custom fields – one for sourcing the value from the search (store value: unchecked) and one with store value: checked – which can be used in the report. And having a workflow update the second field’s value once a day with the value from the first field. But I don’t think this is a best practice as we create two new fields and a workflow. I am working on the saved search now and so far everything looks good.

[Author]

Posts