Migration Guide to ERPNext version 15

Separating Modules from ERPNext to New Apps

Continuing last year's trend some more modules have been moved out as separate apps

• TaxJar Integration
• Exotel Integration
• Lending
• ERPNext France
• Moved E-commerce module from ERPNext to Webshop
• Moved payment gateways from ERPNext to Payments
• Moved KSA localization-specific code to KSA

Following modules were deprecated and later removed entirely from ERPNext:

• Social Media module
• WooCommerce integration

How does this change affect you?

If you are currently not using any of these modules, this change won’t affect you.

However, if you are using any of these modules, when you upgrade to version 15, you will have to install the relevant app on your bench.

From the user's point of view, it won’t make any difference, there will be no loss of functionality.

If you want to raise any new issues or pull requests, you will have to raise them on the respective repository instead of raising them on the ERPNext repository.

- Serial and Batch Bundle

Before version 15 the serial number was a Small Text field in which users were adding multiple serial numbers. The Small Text field has a data integrity issue with the serial number. To solve this issue we have added a separate doctype Serial and Batch Bundle with Serial, Batch as link field. The serial and batch bundle user has to create and link to the child table in the sales, purchase, and stock transactions.

Print format changes

With the new design Serial No / Batch No fields have been replaced with Serial and Batch Bundle link field. With the new Serial and Batch Bundle you won't get the Serial Nos / Batch Nos from the same form. You need to fetch the data from the Serial and Batch Bundle by passing the Serial and Batch Bundle id. To get the information about Serial / Batch Nos in the print format from the Serial and Batch Bundle either you can use the Jinja method get_serial_or_batch_nos(bundle_id) or get the data using frappe.get_all method. For reference kindly check the print format Purchase Receipt Serial and Batch Bundle Print

Standard Print Format for Serial and Batch Bundle will look like as below

If you have custom print format then you can use the below code

<table class="table table-bordered">
	<tbody>
		<tr>
			<th>Sr</th>
			<th>Item Name</th>
			<th>Serial / Batch No</th>
			<th class="text-right">Qty</th>
			<th class="text-right">Rate</th>
			<th class="text-right">Amount</th>
		</tr>
		{%- for row in doc.items -%}
		<tr>
			<td style="width: 3%;">{{ row.idx }}</td>
			<td style="width: 20%;">
				{{ row.item_name }}
				{% if row.item_code != row.item_name -%}
				<br>Item Code: {{ row.item_code}}
				{%- endif %}
			</td>
			<td style="width: 37%;">
				<div style="border: 0px;">{{ get_serial_or_batch_nos(row.serial_and_batch_bundle) }}</div>
			</td>
			<td style="width: 10%; text-align: right;">{{ row.qty }} {{ row.uom or row.stock_uom }}</td>
			<td style="width: 15%; text-align: right;">{{
				row.get_formatted("rate", doc) }}</td>
			<td style="width: 15%; text-align: right;">{{
				row.get_formatted("amount", doc) }}</td>
		</tr>
		{%- endfor -%}
	</tbody>
</table>

User can override the Template of the Serial and Batch Bundle print format using Custom APP

Add get_serial_or_batch_nos method in your custom app's hooks.py file (Check below image)

Write your custom Template code for the Serial and Batch Bundle print in the get_serial_or_batch_nos method and check

Hierarchy Chart moved to Frappe HR

Hierarchy charts were added as generic classes to visualize hierarchies for Org Charts. As it is not being used anywhere in ERPNext as of now, it has been removed in v15 and moved to the hrms repo. html2canvas, a dependency added for exporting org charts to images is also removed from ERPNext.

So if you are using these JS classes or the html2canvas library, you can install hrms or create a custom app for the functionality using these.

Changed behaviour to add Portal Users for Suppliers & Customers

Before v15, the steps for adding a new User to the list of users who can access the Supplier / Customer Portal were as follows -

• Create a Website User with the Supplier / Customer role.
• Create a Contact for the Supplier / Customer which acts like a dynamic link between the User and the Supplier / Customer.

Portal Users can now be added for a particular Supplier / Customer as follows -

• Navigate to the Portal Users tab for the Supplier / Customer.
• Add one or multiple Users to the table of users who can access the Portal.

Note: The appropriate role is added automatically for the User once added to the Portal Users table.

Cashflow Mapper

Cashflow mapper has been deprecated in ERPNext v15 and will no longer be available