Known Issues
Overview
This page displays the known issues reported by the support team.
Know Issues
EPL-1449 Solved
EPL-1449 Gradle loses execution permissions when doing an etendo-restore.
Workaround
Apply the following change in the etendo-restore file to ensure that the gradlew file is excluded from the permission change with chmod:
- find /opt/EtendoERP -type f -exec chmod 644 '{}' \+
+ find /opt/EtendoERP -type f ! -name gradlew -exec chmod 644 '{}' \+
This workaround is applicable if you have deployed Etendo from the ISO in versions prior to 24.1.4. Starting from that version, the issue of permission changes on the gradlew file is no longer observed.
EE-856 Solved
EE-856 390 Tax Report dataset duplicates data for 2022 when applied on a server migrated from OB to Etendo after 01-2023.
Workaround
Warning: The following workaround can vary depending on diverse factors, such as:
- Hand-made taxes
- Hand-made Tax Categories
- Taxes dataset applied in an organization other than *
- Attemps to apply the datasets, previous to doing the workarounds
- etc
If you have some of these caracteristics in your environment, contact with the support team for a custom solution
There are two ways to solve the problem, depending on how the taxes and temporal taxes datasets have been applied before:
-
Temporal Taxes dataset on "individual" organizations, and Taxes dataset at * level:
-
Execute this SQL script, which will do the following:
-
Move the taxes from one of the Oraganizations (the first one where the Temporal Taxes dataset was applied) to *.
-
Update the taxes from the * organization and change their application history IDs (an ID to know which tax was applied), to turn them from the Openbravo ones to the Etendo ones.
-
Update application history IDs for those temporal taxes that have been created on individual organizations, so the dataset importing process does not detect them and does not put data into them.
-
-
Install Taxes dataset at * level. The taxes from the * organization will be updated.
-
Execute the fix script where the 390 duplication problem is solved.
-
Apply the dataset update for the 390 tax model.
-
-
Taxes and Temporal Taxes datasets both applied at * level:
-
Execute the taxes script designed in the issue EE-808.
-
Execute the fix script where the 390 duplication problem is solved.
-
Apply the Taxes dataset update for the corresponding organization.
-
Apply the dataset update for the 390 tax model.
-
EE-808 Solved
EE-808 Problem when trying to import the 'taxes: configuration for Spain' dataset if the environment already has imported the dataset related to the 303 temporary taxes of Openbravo.
Workaround
Warning: The following workaround can vary depending on diverse factors, such as:
- Hand-made taxes
- Hand-made Tax Categories
- Taxes dataset applied in an organization other than *
- Attemps to apply the datasets, previous to doing the workarounds
- etc
If you have some of these caracteristics in your environment, contact with the support team for a custom solution
There are two ways to solve the problem, depending on how the taxes and temporal taxes datasets have been applied before:
-
Temporal Taxes dataset on "individual" organizations, and Taxes dataset at * level:
-
Execute this SQL script, which will do the following:
-
Move the taxes from one of the Oraganizations (the first one where the Temporal Taxes dataset was applied) to *.
-
Update the taxes from the * organization and change their application history IDs (an ID to know which tax was applied), to turn them from the Openbravo ones to the Etendo ones.
-
Update application history IDs for those temporal taxes that have been created on individual organizations, so the dataset importing process does not detect them and does not put data into them.
-
-
Install Taxes dataset at * level. The taxes from the * organization will be updated.
-
-
Taxes and Temporal Taxes datasets both applied at * level:
-
Execute the following script, which will update the taxes from the * organization and change their application history IDs (an ID to know which tax was applied), to turn them from the Openbravo ones to the Etendo ones:
-
Install Taxes dataset at * level. The taxes from the * organization will be updated.
-
The next steps are the same for both cases:
-
Execute the following script, which will update the 303 model, changing their Openbravo IDs to Etendo IDs.
-
Install 303 model dataset at individual organizations level. The corresponding parameters will be inserted in the taxes from * organization, each one associated to their specific individual organization.
EE-758 Solved
EE-758 Incorrect BP Settlement Module Functionality with Payment (In/Out) Combination and Credit Usage.
Attention
The combination of Payments (In/Out) with credit usage in the Business Partner Settlement module is currently experiencing issues. Incorrect values for amount and credit used may result in financial account discrepancies. We advise against combining credit usage with settlement until this issue is resolved.
EPL-858 Solved
EPL-858 Etendo does not compile with latest version of gradle plugin in JAR format.
Workaround
Before execute setup tasks in a etendo project in JAR format you must follow the next steps:
On the source path, open build.gradle
and locate the 'etendo' block in the file. Inside of it, add the following propertie:
This configuration will allow you to download the source of the project on your local environment. It will be needed for following steps.
Now we need to execute the command that will download the source code:
If you don't want to change thebuild.gradle
, you can execute the command ./gradlew expandCore
and add the flag -PforceExpand=true
at the end of it