mirror of
https://github.com/erpnext/foundation.git
synced 2026-10-17 10:20:46 +02:00
docs
This commit is contained in:
@@ -0,0 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,30 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
#Editing Value in Submitted Document
|
||||
|
||||
Once document is submitted, fields are frozen, and no editing is allowd. Still there are certain standard fields like Letter Head, Print Heading which can still be edited. For the custom field, if **Allow on Submit** property is checked, it will be editable even after document is submitted.
|
||||
|
||||
<div class="well"> Standard fields cannot be set as Allow on Submit.</div>
|
||||
|
||||
#### Step 1: Go To
|
||||
|
||||
`Setup > Customize > Customize Form`
|
||||
|
||||
####Step 2: Select Form
|
||||
|
||||
In Customize Form, select Document Type (Quotation, Sales Order, Purchase Invoice Item etc.)
|
||||
|
||||
<img alt="select docytpe" class="screenshot" src="{{docs_base_url}}/assets/img/articles/allow-on-submit-1.png">
|
||||
|
||||
#### Step 3: Edit Field Property
|
||||
|
||||
In the fields section, click on the Custom field and check the **Allow On Submit**.
|
||||
|
||||
<img alt="Check Allow on Submit" class="screenshot" src="{{docs_base_url}}/assets/img/articles/allow-on-submit-2.png">
|
||||
|
||||
#### Step 3: Update Customize Form
|
||||
|
||||
<img alt="Update" class="screenshot" src="{{docs_base_url}}/assets/img/articles/allow-on-submit-3.png">
|
||||
|
||||
After updating Customize Form, you should reload your ERPNext account. Then check form, and field to confirm its editable in submitted form as well.
|
||||
|
||||
<!-- markdown -->
|
||||
@@ -0,0 +1,30 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
#Creating Custom Link Fields
|
||||
|
||||
Links field are the ones linked to another document type. For example, customer field is a link field in Sales Order. This field is linked to the Customer master.
|
||||
|
||||
You can insert Custom Link Field by following steps below.
|
||||
|
||||
|
||||
####Step 1: Go to Customize Form
|
||||
|
||||
`Setup > Customize > Customize Form`
|
||||
|
||||
####Step 2: Select Form
|
||||
|
||||
In Customize Form, select Document Type (Quotation, Sales Order, Purchase Invoice Item etc.). Once field are updated in table, open field before which you wish to insert Custom Field. Then click on "Insert Above" to insert new Custom Field.
|
||||
|
||||
<img alt="Select Docytpe" class="screenshot" src="{{docs_base_url}}/assets/img/articles/link-field-1.gif">
|
||||
|
||||
####Step 4: Custom Field Values
|
||||
|
||||
To set field as Link, enter values as below.
|
||||
|
||||
1. Label: Desired label that user wishes to display in the form.
|
||||
1. Type: Set as 'Link'
|
||||
1. Name: Desired name for the field
|
||||
1. Options: Enter the name of the Doctype to which the field is linked
|
||||
|
||||
<img alt="Enter Values" class="screenshot" src="{{docs_base_url}}/assets/img/articles/link-field-2.png">
|
||||
|
||||
<!-- markdown -->
|
||||
@@ -0,0 +1,27 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
#Customizing Sorting Order in the List View
|
||||
|
||||
**Question:** I want records in my Item List sorted based on Desc Order of Item Code.
|
||||
|
||||
**Answers:** Following are the steps to customize Sort Order for the Item master. These steps will be applicable for customizing Sort Order for the other documents as well.
|
||||
|
||||
####Step 1: Go to Customize Form
|
||||
|
||||
`Setup > Customize > Customize Form`
|
||||
|
||||
####Step 2: Select Doctype
|
||||
|
||||
Select document type for which Sort Order is to be customized.
|
||||
|
||||
<img alt="Sort Order field" class="screenshot" src="{{docs_base_url}}/assets/img/articles/sort-order-2.png">
|
||||
|
||||
####Step 3: Update Sort Details
|
||||
|
||||
In the Customize Form, you will find these fields.
|
||||
|
||||
<img alt="Sort Order field" class="screenshot" src="{{docs_base_url}}/assets/img/articles/sort-order-1.png">
|
||||
|
||||
1. Sort Field: Select field based on which sorting will be done. It will be "Item_Code" field in scenario.
|
||||
2. Sort Order: Sort Order will be two possible options, **Asc** for ascending, and **Desc** for descending.
|
||||
|
||||
<!-- markdown -->
|
||||
@@ -0,0 +1,24 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
#Deleting Custom Reports
|
||||
|
||||
ERPNext has several [types of reports]({{docs_base_url}}/user/manual/en/customize-erpnext/articles/making-custom-reports-in-erpnext) which can be customize as per the companies/users requirement.
|
||||
|
||||
If there is a report custom report which needs to be deleted, it can be achieved by following steps. Please note that its applicable only for the Custom Reports, and not for the standard reports.
|
||||
|
||||
#### Step 1: Go to Report List
|
||||
|
||||
In the Awesome Bar, type and select "Report List" for an option.
|
||||
|
||||
<img alt="Report Search" class="screenshot" src="{{docs_base_url}}/assets/img/articles/delete-report-1.png">
|
||||
|
||||
####Selecting and Deleting Report
|
||||
|
||||
The Report List will have all the standard and custom reports of your account. You can select Custom Report to be deleted from the list itself, and click on Delete icon.
|
||||
|
||||
<img alt="Report List" class="screenshot" src="{{docs_base_url}}/assets/img/articles/delete-report-2.png">
|
||||
|
||||
Or you can open that report, and delete it from File menu option.
|
||||
|
||||
<img alt="Report Delete" class="screenshot" src="{{docs_base_url}}/assets/img/articles/delete-report-3.png">
|
||||
|
||||
<!-- markdown -->
|
||||
@@ -0,0 +1,24 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
#Disable Rounded Total
|
||||
|
||||
All the sales transactions like Sales Order, Sales Invoice has Rounded Total in it. It calculated based on the value of Grand Total. Also Rounded Total is also visible in the Standard Print Formats.
|
||||
|
||||
<img alt="Print Preview" class="screenshot" src="{{docs_base_url}}/assets/img/articles/hide-rounded-total-1.png">
|
||||
|
||||
Follow steps given below to hide rounded total from Standard Print Formats, for all the sales transactions.
|
||||
|
||||
#### Step 1: Global Settings
|
||||
|
||||
`Setup > Settings > Global Settings`
|
||||
|
||||
#### Step 2: Disable Rounded Total
|
||||
|
||||
Check Disable Rounded Total, and Save Global Defaults.
|
||||
|
||||
<img alt="Print Preview" class="screenshot" src="{{docs_base_url}}/assets/img/articles/hide-rounded-total-2.png">
|
||||
|
||||
For system to take effect of this setting, you should clear cache and refresh your ERPNext account. Then your print formats shall not render value for the Rounded Total in the print formats.
|
||||
|
||||
<div class=well>Note: This setting will only affect Standard print formats.</div>
|
||||
|
||||
<!-- markdown -->
|
||||
@@ -0,0 +1,88 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
#Field Types
|
||||
|
||||
Following are the types of fields you can define while creating new ones, or while amend standard ones.
|
||||
|
||||
- Attach:
|
||||
|
||||
Attach field allows you browsing file from File Manager and attach in the transaction.
|
||||
|
||||
- Button:
|
||||
|
||||
It will be a Button, on clicking which you can execute some functions like Save, Submit etc.
|
||||
|
||||
- Check:
|
||||
|
||||
It will be a check box field.
|
||||
|
||||
- Column Break
|
||||
|
||||
Since ERPNext has multiple column layout, using Column Breaks, you can divide set of fields side-by-side.
|
||||
|
||||
- Currency
|
||||
|
||||
Currency field holds numeric value, like item price, amount etc. Currency field can have value upto six decimal places. Also you can have currency symbol being shown for the currency field.
|
||||
|
||||
- Data
|
||||
|
||||
Data field will be simple text field. It allows entering value upto 255 characters.
|
||||
|
||||
- Date and Time
|
||||
|
||||
This field will give you date and time picker. Current date and time (as provided by your computer) is set by default.
|
||||
|
||||
- Dynamic Link
|
||||
|
||||
Click [here]({{docs_base_url}}/user/manual/en/customize-erpnext/articles/managing-dynamic-link-fields.html) to learn how Dynamic Link Field function.
|
||||
|
||||
- Float
|
||||
|
||||
Float field carries numeric value, upto six decimal place. Precision for the float field is set in
|
||||
|
||||
`Setup > Settings > System`
|
||||
|
||||
Setting will be applicable on all the float field.
|
||||
|
||||
- Image
|
||||
|
||||
Image field will render an image file selected in another attach field.
|
||||
|
||||
For the Image field, under Option (in Doctype),field name should be provide where image file is attached. By referring to the value in that field, image will be reference in the Image field.
|
||||
|
||||
- Int (Integer)
|
||||
|
||||
Integer field holds numeric value, without decimal place.
|
||||
|
||||
- Link
|
||||
|
||||
Link field is connected to another master from where it fetches data. For example, in the Quotation master, Customer is a Link field.
|
||||
|
||||
- Password
|
||||
|
||||
Password field will have decode value in it.
|
||||
|
||||
- Read Only
|
||||
|
||||
Read Only field will carry data fetched from another form, but they themselves will be non-editable. You should set Read Only as field type if its source for value is predetermined.
|
||||
|
||||
- Section Break
|
||||
|
||||
Section Break is used to divide form into multiple sections.
|
||||
|
||||
- Select
|
||||
|
||||
Select will be a drop-down field. You can add muliple results in the Option field, separated by row.
|
||||
|
||||
- Small Text
|
||||
|
||||
Small Text field carries text content, has more character limit than the Data field.
|
||||
|
||||
- Table
|
||||
|
||||
Table will be (sort of) Link field which renders another docytpe within the current form. For example, Item table in the Sales Order is a Table field, which is linked to Sales Order Item doctype.
|
||||
|
||||
- Text Editor
|
||||
|
||||
Text Editor is text field. It has text-formatting options. In ERPNext, this field is generally used for defining Terms and Conditions.
|
||||
|
||||
<!-- markdown -->
|
||||
@@ -0,0 +1,26 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
#Increase Max Attachments
|
||||
|
||||
In ERPNext, you can limit how many files can be attached to specific Document. Using Custmize Form, you can set **Max(imum) Attachments** which can be added to a particular documents.
|
||||
|
||||
Let's assume we need to update Max Attachment for Quotation to five.
|
||||
|
||||
#### Step 1: Setup
|
||||
|
||||
`Setup > Customize > Customize Form`
|
||||
|
||||
#### Step 2: Select Document Type
|
||||
|
||||
<img alt="Select Doctype" class="screenshot" src="{{docs_base_url}}/assets/img/articles/max-attachment-1.png">
|
||||
|
||||
#### Step 3: Set Limit
|
||||
|
||||
Set Maximum Attachments as five.
|
||||
|
||||
<img alt="Set Max Attachment" class="screenshot" src="{{docs_base_url}}/assets/img/articles/max-attachment-2.png">
|
||||
|
||||
After update Max Attachments, Update Customization Form. Reload your ERPNext account and then check specific Quotation to confirm if Max Attachment limit is applied.
|
||||
|
||||
<div class="well">Note: Maximum limit/size of an attachment is 1MB.</div>
|
||||
|
||||
<!-- markdown -->
|
||||
@@ -0,0 +1,2 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
{index}
|
||||
@@ -0,0 +1,17 @@
|
||||
allow-fields-to-be-changed-after-submit
|
||||
creating-custom-link-field
|
||||
customizing-sorting-order-in-the-list-view
|
||||
deleting-custom-reports
|
||||
disable-rounded-total
|
||||
field-types
|
||||
increase-max-attachments
|
||||
make-field-visible-in-print-format
|
||||
making-custom-reports-in-erpnext
|
||||
managing-dynamic-link-fields
|
||||
module-visibility
|
||||
perm-level-error-in-permission-manager
|
||||
search-record-by-specific-field
|
||||
set-language
|
||||
set-precision
|
||||
user-restriction
|
||||
maximum-numbers-of-fields-in-a-form
|
||||
@@ -0,0 +1,28 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
#Make Fields Visible In Print Format
|
||||
|
||||
Each transaction has Standard Print Format. In the Standard format, only certain fields are displayed by default. If user needs field in the Standard format to be visible, it can be customized by using Customize Form tool.
|
||||
|
||||
Let's assume in the Sales order, we need to make Shipping Address field visible in the standard print format.
|
||||
|
||||
#### Step 1: Customize Form
|
||||
|
||||
Go to:
|
||||
|
||||
`Setup > Customize > Customize Form`
|
||||
|
||||
#### Step 2: Document Type
|
||||
|
||||
As per our scenario, Sales Order will be selected as Document Type.
|
||||
field-visible-2.gif
|
||||
<img alt="Document Type" class="screenshot" src="{{docs_base_url}}/assets/img/articles/print-visible-1.png">
|
||||
|
||||
#### Step 3: Uncheck Print Hide
|
||||
|
||||
click to open field to be made visible in the Standard Print Format. Uncheck **Print Hide** field.
|
||||
|
||||
<img alt="Uncheck Print Hide " class="screenshot" src="{{docs_base_url}}/assets/img/articles/print-visible-2.gif">
|
||||
|
||||
#### Step 4: Update
|
||||
|
||||
Update Customize Form to save changed. Reload your ERPNext account, and then check Print Format for confirmation.
|
||||
@@ -0,0 +1,24 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
#Reports in ERPNext
|
||||
|
||||
There are three kind of reports in ERPNext.
|
||||
|
||||
###1. Report Builder
|
||||
|
||||
Report Builder is an in-built report customization tool in ERPNext. This allows you to define specific fields of the form which shall be added in the report. Also you can set required filters, sorting and give preferred name to report.
|
||||
|
||||
<iframe width="660" height="371" src="https://www.youtube.com/embed/y0o5iYZOioU" frameborder="0" allowfullscreen></iframe>
|
||||
|
||||
### 2. Query Report
|
||||
|
||||
Query Report is written in SQL which pull values from account's database and fetch in the report. Though SQL queries can be written from front end, like HTML, its restricted in hosted users. Because it will allow users with no access to specific report to query data directly from the database.
|
||||
|
||||
Check Purchase Order Item to be Received report in Stock module for example of Query report. Click [here](https://frappe.io/docs/user/en/guides/reports-and-printing/how-to-make-query-report.html) to learn how to create Query Report.
|
||||
|
||||
### 3. Script Report
|
||||
|
||||
Script Reports are written in Python and stored on server side. These are complex reports which involves logic and calculation. Since these reports are written on server side, customizing it from hosted account is not possible.
|
||||
|
||||
Check Financial Analytics report in Accounts module for example of Script Report. Click [here](https://frappe.io/docs/user/en/guides/reports-and-printing/how-to-make-script-reports.html) to learn how to create Script Report.
|
||||
|
||||
<!-- markdown -->
|
||||
@@ -0,0 +1,49 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
#Managing Dynamic Link Fields
|
||||
|
||||
Dynamic Link field is one which can search and hold value of any document/doctype. Let's consider an example to learn how Dynamic Link field works.
|
||||
|
||||
While creating Opportunity or Quotation, we have to explicitly define if it is for Lead or Customer. Based on our selection (Lead/Customer), another link field shows up where we can select actual Lead or Customer.
|
||||
|
||||
If you set former field as Dynamic Link, where we select actual Lead or Customer, then the later field will be linked to master selected in the first field, i.e. Leads or Customers. Hence we need not insert separate link fields for Customer and Lead.
|
||||
|
||||
Below are the steps to insert Custom Dynamic Field. For an instance, we will insert Dynamic Link Field in Journal Entry.
|
||||
|
||||
#### Step 1: Insert Link Field for Doctype
|
||||
|
||||
Firstly we will create a link field which will be linked to the Doctype.
|
||||
|
||||
<img alt="Custom Link Field" class="screenshot" src="{{docs_base_url}}/assets/img/articles/dynamic-field-1.gif">
|
||||
|
||||
By **Doctype** mentioned in the Option field, we mean parent Doctype. So, just like Quotation is one Doctype, which has multiple Quotation under it. Same way, Doctype is also a Doctype which has Sales Order, Purchase Order and other doctypes created as Doctype records.
|
||||
|
||||
-- Doctype<br>
|
||||
---- Sales Order<br>
|
||||
---- Purchase Invoice<br>
|
||||
---- Quotation<br>
|
||||
---- Sales Invoice<br>
|
||||
---- Employee<br>
|
||||
---- Production Order<br>
|
||||
.. and so on.
|
||||
|
||||
So linking this field with parent Doctype will list all the Doctype records.
|
||||
|
||||
<img alt="journal Voucher Link Field" class="screenshot" src="{{docs_base_url}}/assets/img/articles/dynamic-field-2.png">
|
||||
|
||||
#### Step 2: Insert Dynamic Link Field
|
||||
|
||||
This custom field's type will be "Dynamic Link". In the Option field, name of Doctype link field will be mentioned.
|
||||
|
||||
<img alt="Custom Dynamic Field" class="screenshot" src="{{docs_base_url}}/assets/img/articles/dynamic-field-3.gif">
|
||||
|
||||
This field will allow selecting document id, based on value selected in the Doctype link field. For example, if we select Sales Order in the prior field, Dynamic Link field will list all the Sales Orders ids.
|
||||
|
||||
<img alt="Custom Dynamic Field" class="screenshot" src="{{docs_base_url}}/assets/img/articles/dynamic-field-4.gif">
|
||||
|
||||
<div class="well">
|
||||
**Customizing options in the Doctype Link field**
|
||||
|
||||
By default, Docytpe link field will provide all the forms/doctypes for selection. If you wish this field to show certain specific doctypes in the search result, you will need to write Custom Script for it.
|
||||
</div>
|
||||
|
||||
<!-- markdown -->
|
||||
@@ -0,0 +1,23 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
Sometimes while creating custom fields, you might experienced an error message like below:
|
||||
|
||||
> Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs
|
||||
|
||||
### What it actually means?
|
||||
|
||||
In simple terms, it means that you have reached the limit of maximum numbers of fields for the specific form/doctype. So, what is the limit of maximum numbers of fields?
|
||||
|
||||
In MySQL, there is a hard limit of 4096 columns per table, but the effective maximum may be less for a given table. The exact limit depends on several interacting factors.
|
||||
|
||||
Every table (regardless of storage engine) has a maximum row size of 65,535 bytes. Storage engines may place additional constraints on this limit, reducing the effective maximum row size.
|
||||
|
||||
The maximum row size constrains the number (and possibly size) of columns because the total length of all columns cannot exceed this size (65,535 bytes). For example, `utf8mb3` characters require up to 3 bytes per character, so for a `VARCHAR(140)` column, the server must allocate `140 × 3 = 420` bytes per value. Consequently, a table cannot contain more than `65,535 / 420 = 156` such columns.
|
||||
|
||||
In Frappe frapework, `VARCHAR(140)` type columns are created based on "Data", "Link", "Select", "Dynamic Link", "Password" and "Read Only" fieldtypes. Hence, you can create approximately 156 such columns in the system.
|
||||
|
||||
### Solutions:
|
||||
|
||||
To add more fields in the system, you can do some changes.
|
||||
|
||||
1. Convert some of the fields to "Text", "Small Text", "Text Editor" or "Code" type field. In MySQL, BLOB and TEXT columns count from one to four plus eight bytes each toward the row-size limit because their contents are stored separately from the rest of the row. So, converting to those fieldtypes will free up some spaces and will allow to add some more fields.
|
||||
2. Set smaller value in the "Length" property while creating fields, default value is 140. System sets length of `VARCHAR` based on this property and allocates size for that columns. Hence, smaller Length leads to add more fields.
|
||||
@@ -0,0 +1,20 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
#Module Visibility
|
||||
|
||||
If you have permission on specific module, but it is still not visible, following are the possibilities of issues you should look at. Let's consider a scenario that user is permission of Website module, but not able to access it.
|
||||
|
||||
As step zero, ensure that you have "Website Manager" role assigned. It is a standard Role which grants permission on Website module. If permissions has been customized in your account, check Role Permission Manager to know which Role has permission on Website, and then check if same Role is assigned to User.
|
||||
|
||||
If module is hidden in-spite of assignment of required Role, then you should check if Website is not disabled from All Application.
|
||||
|
||||
<img alt="All Applications" class="screenshot" src="{{docs_base_url}}/assets/img/articles/module-visibility-1.gif">
|
||||
|
||||
If Website is checked in All Application, but still not visible for the User, check if is hidden by System Manager. In the Setup module, feature called Show/Hide Modules allows System Manager to hide specific module from all the Users.
|
||||
|
||||
`Setup > Settings > Show / Hide Modules`
|
||||
|
||||
Ensure Website module is checked. If you just enabled/activated it, update Show/Hide Module page, and then Reload tab of your ERPNext account. After reload, changes made in the Setup module will be applied and will be visible in the system.
|
||||
|
||||
On the same lines, you can check for the visibility issue of other modules as well.
|
||||
|
||||
<!-- markdown -->
|
||||
@@ -0,0 +1,20 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
#Perm Level Error in Permission Manager
|
||||
|
||||
While customizing rules in the [Permission Manager]({{docs_base_url}}/user/erpnext/user/manual/en/setting-up/users-and-permissions/role-based-permissions), you might receive an error message saying:
|
||||
|
||||
`For System Manager _(or other role)_ at level 2 _(or other level)_ in Customer _(or other document)_ in row 8: Permission at level 0 must be set before higher levels are set.`
|
||||
|
||||
Error message indicates problem is in the existing permission setting for this document.
|
||||
|
||||
For any role, before assigning permission at Perm Level 1 or 2 (and so on), permission at Perm Level 0 must be assigned. Error message says that System Manager has been assigned permission at Perm Level 1 and 2, but not at level 0. You should first correct the permission for System Manager's role by:
|
||||
|
||||
- Assigning permission to System Manager at level 0.
|
||||
|
||||
Or
|
||||
|
||||
- By removing permission at level 1 and 2.
|
||||
|
||||
After executing one of the above step, you should be able to successfully add new permissions rules in the Role Permission Manager.
|
||||
|
||||
<!-- markdown -->
|
||||
@@ -0,0 +1,28 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
#Search Record by Specific Field
|
||||
|
||||
While creating any document (say Sales Invoice), you have to select other document id in it (say Serial No). For ease in selection, you can also make value of other field of that visible in the search result. Search By functionality enables to define field whos value will be visible in the search result.
|
||||
|
||||
Let's assume that while creating Sales Invoice, you wish to see Serial No result, with respective Warehouse.
|
||||
|
||||
#### Step 1: Customize Form
|
||||
|
||||
`Setup > Customize > Customize Form`
|
||||
|
||||
#### Step 2: Select Document
|
||||
|
||||
`Document Type = Serial No.`
|
||||
|
||||
#### Step 3: Search Field
|
||||
|
||||
Update Warehouse field name in the Search By field.
|
||||
|
||||
<img alt="Search By in Customize Form" class="screenshot" src="{{docs_base_url}}/assets/img/articles/search-by-1.png">
|
||||
|
||||
#### Searching in Another Record.
|
||||
|
||||
While creating transaction, to get filtered result for Customer, you should firstly click on search magnifier.
|
||||
|
||||
<img alt="Search By in Customize Form" class="screenshot" src="{{docs_base_url}}/assets/img/articles/search-by-2.png">
|
||||
|
||||
<!-- markdown -->
|
||||
@@ -0,0 +1,43 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
#Change the Language
|
||||
|
||||
ERPNext is an multi-lingual application. It allows each user to select preferred lannguage. Following is how User can customize language in one's account.
|
||||
|
||||
### 1. Setting Language in User's Account
|
||||
|
||||
Following are the steps to set language in your ERPNext account.
|
||||
|
||||
#### 1.1 Go to My Setting
|
||||
|
||||
<img alt="My Setting" class="screenshot" src="{{docs_base_url}}/assets/img/articles/change-language-1.png">
|
||||
|
||||
#### 1.2 Select Language
|
||||
|
||||
<img alt="Select Language" class="screenshot" src="{{docs_base_url}}/assets/img/articles/change-language-2.png">
|
||||
|
||||
<img alt="Select Language" class="screenshot" src="{{docs_base_url}}/assets/img/articles/set-language-1.gif">
|
||||
|
||||
#### 1.3 Save User
|
||||
|
||||
On saving User after selecting language, your ERPNext account will be refresh automatically. Then you will see ERPNext translated in your selected language.
|
||||
|
||||
Being a System Manager, you can set language in other user's master as well.
|
||||
|
||||
### 2. Set Language Globally for an Account
|
||||
|
||||
#### 2.1 Go to Setup
|
||||
|
||||
`Setup > Settings > System Settings`
|
||||
|
||||
#### Set Language
|
||||
|
||||
<img alt="Global Language" class="screenshot" src="{{docs_base_url}}/assets/img/articles/change-language-3.png">
|
||||
|
||||
#### Save
|
||||
|
||||
Save System Settings, and refresh your EPRNext account. On refreshing, you should language in your ERPNext account changed as per your preference.
|
||||
|
||||
<img alt="Select Language" class="screenshot" src="{{docs_base_url}}/assets/img/articles/set-language-2.gif">
|
||||
|
||||
Note: For now, we have translation available only for few languages. You can contribute to make translation better, and add new languages from [here](https://translate.erpnext.com).
|
||||
<!-- markdown -->
|
||||
@@ -0,0 +1,19 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
#Set Precision
|
||||
|
||||
In ERPNext, default precision for `Float`, `Currency` and `Percent` field is three. It allows you to enter value having value upto three decimal places.
|
||||
|
||||
You can also change/customize the precision settings globally or for a specific field.
|
||||
|
||||
To change the precision globally, go to:
|
||||
|
||||
`Setup > Settings > System Settings`.
|
||||
|
||||
<img alt="Global Precision" class="screenshot" src="{{docs_base_url}}/assets/img/articles/precision-1.png">
|
||||
|
||||
You can also set field specific precision. To do that go to `Setup > Customize > Customize Form` and select the DocType there. Then go to the specific field row and change precision. Precision field is only visible if field-type is one of the Float, Currency and Percent.
|
||||
|
||||
<img alt="Field-wise Precision" class="screenshot" src="{{docs_base_url}}/assets/img/articles/precision-2.png">
|
||||
|
||||
|
||||
<!-- markdown -->
|
||||
@@ -0,0 +1,20 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
# Restricting based on Owner
|
||||
|
||||
Following are the steps to restrict User to a document based on Owner/creator.
|
||||
|
||||
#### Step 1: Role Permission Manager
|
||||
|
||||
`Setup > Permissions > Role Permissions Manager`
|
||||
|
||||
#### Step 2: Select Document Type
|
||||
|
||||
Select Document Type for which you want to set user permission. After permissions are loaded for selected document, scroll to role for which you want to set restriction.
|
||||
|
||||
<img alt="Sales Order" class="screenshot" src="{{docs_base_url}}/assets/img/articles/owner-restriction-1.png">
|
||||
|
||||
#### Step 3: Apply User Permission
|
||||
|
||||
For Role to be restricted (Sales User in this case), check "If Owner".
|
||||
|
||||
<img alt="S" class="screenshot" src="{{docs_base_url}}/assets/img/articles/owner-restriction-2.png">
|
||||
Reference in New Issue
Block a user