Help Articles For ERPNext Part 2
Deleting Custom Reports
In ERPNext v16, you may make many different types of reports, such as Standard Reports, Query Reports, Script Reports, and Custom Reports. Users generate Custom Reports by altering regular reports to fit their own business needs. If you don’t need a custom report anymore, you can safely delete it. It won’t change the report that it is based on.
Please remember that you can only delete Custom Reports. You can’t delete the regular reports that come with ERPNext.
Open the Report List in Step 1
To see all the reports in your ERPNext system, use the Awesome Bar, which is the search bar at the top of the screen.
Find “Report List” and click on it.
The Report List page shows all of the reports, both the ones that ERPNext sends you and the ones that users produce themselves.
Step 2: Remove the report from the list
Find the Custom Report in the Report List and click on it to delete it. Custom reports are usually marked by the type of report or the way they are named.
There are a few ways to get rid of the report:
- In the view of the Report List:
- Pick the custom report.
- In the Actions Menu, click on the three dots.
- Click the Delete icon to get rid of the report for good.
- From inside the report:
- Open the report you made.
- Open the files menu.
- Click Delete to get rid of the report.
When you delete the custom report, it won’t show up in the report list or be available to users anymore. If it is needed again, it must be created by hand from the original standard report.
Restore Deleted Documents
Use Case: You need to obtain back documents that you mistakenly erased or that you need again for reference, an audit, or extra work. The Deleted Documents log in ERPNext v16 lets users restore deleted documents if they have the necessary permissions.
Steps:
- To discover “Deleted Documents,” go to Settings and then click on “Deleted Documents.”
This page has a complete list of all deleted records, including the DocType, the original name, the time of deletion, and the person who removed it.
- Find the file that was deleted. You may further narrow down the results by filtering the list by Deleted DocType.
For example, if you need to restore a Purchase Order with the name PUR-ORD-2026-00012, select Purchase Order as the Deleted DocType, look through the list for the record, and open it to see its data.
- Click the “Restore” button on the Deleted Document form, as indicated.
Before recovering the document, look at the Data section to see the field values that are saved in it, such as items, quantities, amounts, and references. This enables you make sure that the document you are recovering is the right one.
- When you click the Restore button, the document is restored in Draft state with a new name depending on the current Naming Series for that DocType. This behaviour makes sure that restored documents don’t clash with records that are already there.
- You can either click the “Open” button to open the document straight away or look for it in the right document list (like the Purchase Order list) when you restore it. You can then modify, send, or conduct extra work on the restored document as needed for your business.
Duplicate Records
The “Duplicate” feature in ERPNext v16 enables you copy all the field values from an existing document to produce a new one. You don’t have to enter the same data over and over again, which saves you time and effort. However, you may still alter the new document before you save or email it.
Scenario
An electronics supplier has been asked by a customer to send them additional of several things.
The provider can just access the original Sales Order and choose the Duplicate option. The new Sales Order will have most or all of the same information as the original, such as client details, items, quantities, pricing, taxes, and terms. ERPNext will create a new Sales Order with the same information as the old one. This will make sure that the orders are always the same and that they are made faster. You can then make any adjustments you need to, such as modifying the amounts, delivery dates, or prices, before saving or emailing the revised document.
To copy a document, open the original and click “Duplicate” in the Menu or Drop-Down menu.
The system will create a new document in Draft status with a new name based on the naming sequence you set up. You can then look over, change, and finish the transaction without altering the original record.
Checking Link Between Documents
You can connect any document in ERPNext v16 to one or more other documents as part of a business workflow. These links assist keep track of transactions, make sure data is consistent, and make it easier to identify how records are connected at different points in time, such as bids, orders, invoices, deliveries, and payments.
With the “Links” feature, you can easily see if the current document is related to any other papers and see all the links that were made from it. Most of the time, forward links go to documents that were made or utilised as a reference for the present document. This helps you remember what transactions take place after this document.
To see these links, open the document and click “Links” in the Menu/Drop-Down. A pop-up window will appear with a list of all the documents that are directly related to or were made from the one you are now looking at. You will be able to easily find the names and types of these papers.
This choice only shows links to the next document from the one you are now looking at. In the document itself, the relevant reference fields usually indicate backward connections, which are documents that the present document came from.
To check which Sales Invoices or Delivery Notes are linked to a Sales Order, go to the Sales Order drop-down menu and choose “Links.” But the Sales Order document will have information about the Quotation that the Sales Order was based on, since it is a link that goes back.
Filter Options in Select Field
You can use Client Scripts in ERPNext v16 to dynamically filter Select fields based on what you choose in another field. This is especially useful when you want to limit the choices users can make, make sure the data is correct, and make it easier to enter data by only providing alternatives that are relevant to the circumstance.
For example, there are two drop-down (Select) fields called Town and Nation. Values for the Nation field include England and Scotland, while values for the Town field include London, Manchester, Edinburgh, and Glasgow. You can develop a custom Client Script that adjusts the options based on the value chosen. This will make the Town field show only Towns that are relevant to the Nation chosen.
In that manner, users will not be able to choose incompatible values (like choosing London when England is chosen) that makes the master and transactional data cleaner and more precise.
This is one such custom code that restricts the values in the Select field of a child table:
frappe.ui.form.on(‘Parent DocType’, {
refresh: function (frm) {
// Trigger this function when the form is refreshed or reloaded
frm.fields_dict[‘child_table_fieldname’].grid.get_field(‘select_fieldname’).get_query = function(doc, cdt, cdn) {
return {
filters: [
[‘Some Field’, ‘=’, ‘Some Value’] // Replace with your filter criteria
]
};
};
}
});
An Example
Suppose you now have a DocType which is Sales order and a child table field which is Items. The Select column in this child table is called Item Category (or another similar name). You would prefer to restrict the options that it provides you to the ones that work in a particular condition, such as a specific category, warehouse or type of client.
This type of filtering is normally employed by people in cases where the choices in a child row are determined by the choices made in the parent document or in another field of a child row. It simplifies the usage and prevents individuals to store the inappropriate sets of values.
An example of what your script may look like is given below:
frappe.ui.form.on(‘Sales Order’, {
refresh: function (frm) {
frm.fields_dict[‘items’].grid.get_field(‘item_code’).get_query = function(doc, cdt, cdn) {
return {
filters: [
[‘Item Group’, ‘=’, ‘Specific Category’] // Adjust the filter criteria as needed
]
};
};
}
});
In ERPNext v16, you would normally add this logic using Client Scripts. Make sure the script points to the proper DocType and child table field so that the filtering happens automatically as users fill out the form.
