Hello community, came across a weird use case, and really would like to see this get done
I’d like to bring “different currency” to the items listed in “Supplier Quotation Items” as well as “Quotation Items”.
For example, item-code #1 will only be rated in USD, while item-code #2 will be rated only in EUR, but in a same quotation. And the total will be calculated in the company currency in the parent DocType.
I already started editing the DocTypes for experimenting, so no worries if you provide a hack
Well, thanks for the reply but your suggestion doesn’t/wouldn’t work since we have to give the currency in Quotation itself, but not to the Items in the quotation.
I’m trying to achieve so that Grand Total is always shown in company currency (in the quotation), but the items that are inside the quotation are shown in different currencies individually
I have to set a few items with multiple price list entries and give it a try. The idea is to get the items in the price lists and then be able to access the price in the desired currency for each item. Customizing the form will follow. This link might also be useful:
Right, I’m deep into customizing the forms, ahem, I mean the DocTypes, so as long as I get the results I wouldn’t mind any hacks or just about anything at this moment
When you say you have to set a few items with multiple currencies etc, you mean you’re going to try it on your ERPNext installation and see for yourself? Oh boy, I would really really appreciate it!
Hi @iMoshi@smino I also have the same concern. Do you think if it is possible to make the currency, exchange rate, and pricelist visible on the item rows?
I haven’t tested it and I am not sure how to execute it.
This is the solution I can think of to select the correct price based on the item pricelist and then encode the exchange rate per item so that it will be converted to the currency of the transaction.
We have created a custom app for our use and we have it implemented. You should first create a new custom DocType, and a child DocType for it. Then give it (the child doctype) the currency field, exchange rate etc fields. Somehow they’d have to make some calculations on the parent doctype and that’s where you need lots of custom JS.