apnabloghe

It is good to know that in ERPNext, custom print formats do not automatically display the header and footer. You can set the header as follows: {% if letter_head and not no_letterhead -%} {% if print_settings.repeat_header_footer %} <br> <div class="letter-head">{{ letter_head }}</div> {%- endif %}{%- endif %} You should follow a similar approach for the footer. However, one thing to keep in mind is that the system offers translations only for the built-in (Standard) print formats. If you create a custom print format (based on an existing one), the labels must be entered in English as follows: {{ _("Field Label Text in English") }} Later, you can use the ERPNext built-in translation tool to translate the labels into your desired language.

As usual, I followed the news and developments about ERPNext and Frappe version 14 even before its release, and I couldn’t wait to try it out. After getting acquainted with the developer version, I also tested the official release, and although I didn’t encounter any issues, as is advisable in such cases, we didn’t immediately upgrade to the latest version. As I mentioned in the  previous post , there were no issues with new installations, but a few bugs appeared during the upgrade from the previous version. Now, it seemed like enough time had passed for any potential bugs to be fixed, so we decided to proceed with the upgrade today. Normally, the  Frappe Cloud  handles this for us, which used to require a support ticket from them in the past, but now it’s automated. You can specify the scheduled date for the ERPNext/Frappe upgrade. I did the same, but unfortunately, I wasn’t successful. The reason was that due to a certain customization, the automatic upgrade to the new ...

This year, the ERPNext conference organized by Frappe placed emphasis on in-person attendance, and there was no online broadcast. However, they recorded various high-quality presentations, which will be edited and published later. Once they become available, I will share more information. For now, we could get a glimpse of the presentations on Twitter, as the conference program covered various topics:  https://conference.erpnext.com/ One highlight was the inclusion of several headless presentations alongside various introductions and feature demonstrations. Another important aspect was that although version 14 broke away from the monolithic development principle, as I mentioned before, it moved towards a module-based development concept: not only do they maintain the concept of ERPNext being a full-featured free and open-source ERP system, but they also structure the modules in a way that they can be used independently. A good example is the HR app presented at the conference, whic...

One of our colleagues encountered difficulties with indexing the ERPNext website on Google, so I checked the situation and found that our website has been indexed by Google so far, as it was not blocked. But there are ways to improve it further. There is an option to notify Google of every new content published so that it can crawl and display it as a search result on its search page. I decided to write this article because although this feature exists, the documentation is incomplete. If we want to enable this indexing, we first need to set up Google services within our ERPNext system, and for this, we also need to configure certain things in the Google Developer Console, which is well documented. However, besides using the credentials for címtár, naptár, map, drive API, and Google OAuth, we also need to enable the Indexing API. Once this is done, the crucial step is to set the following as the Authorized Redirect URIs within the OAuth 2.0 Client IDs of the used credentials: https://w...

This is just a short note in response to a frequently asked question about how to correct the cost center fields on submitted documents, typically on invoices, when they are missing or set incorrectly. The general answer to this is that it cannot be done. This is because ERPNext is based on a double-entry accounting system, which must ensure the integrity of the data. Also, these documents should ideally be submitted after careful review by someone familiar with the specific area to ensure they are error-free. Alternatively, you can set up the automation correctly to allow users without specific knowledge to submit documents they are entitled to. Thus, correcting the cost center setting of the original transaction is not possible. What options do we have to handle this limitation then? One option is to void the incorrect document and create a new one with the correct cost center information, keeping the original date. However, this can be done correctly only if the period has not been ...

  For an ERP and business management system, it is critical to be always available and functional when needed. The need for this depends on the peculiarities of the business. In the industry, we have been talking about 24/7 operations for a long time, but when is it possible to keep a continuously evolving system up-to-date without missing out on emerging and useful features? This is where the integrated solution in the Frappe framework, which is also used by ERPNext, comes into play by introducing the read-only mode for systems under maintenance. What does this mean? Traditionally, during updates and maintenance, ERPNext and Frappe were not accessible to users. This new feature now allows limited access to the system even during maintenance. Users can log in and access data but cannot make any changes or enter new transactions to maintain data consistency. So, is this a true zero-downtime solution? Indeed, it is not entirely zero-downtime, but we mention it this way because previo...

There was a previous post about exchange rates where I presented the basic ERPNext exchange rate API connections, which was particularly useful for those who want to use the exchange rates from the European Central Bank since they declared it in their accounting policy and to the National Tax and Customs Administration (NAV). There can be advantages and disadvantages to this, just as with using your own bank’s exchange rates. The important thing is that ERPNext offers options for everything, as you can manually enter any exchange rate, but who wants to manually enter exchange rates when they can be automatically retrieved from the appropriate source, such as the MNB webservice, and it’s free? Since most companies use MNB exchange rates, you can say it’s the standard, so even though I recommended the simpler EKB solution, we can’t avoid the MNB exchange rates. Therefore, one of the first steps in implementing the features of my ERPNext Hungarian invoicing solution was to develop MNB int...