When the current translation field is edited in the company attribute translation window for an account, the account description cannot be changed from the accounts window. This behavior can be observed in other windows too: tax codes window, customer invoice types, supplier invoice types.Is it possible somehow to change such descriptions in desired languages? There is a workaround. But it is not effective too in certain instances.Workaround is: If the account description needs to be edited, use the company attribute translation window and change the relevant row with the language code.If more languages are used as the login language, then, add them to the ‘Company attribute translations’ window and edit the current translations of those as well. Issue with the suggested workaroundIf the user login from a language which is not defined in the company attribute translation window, then the old account number is shown. (If it’s a system defined account, then the system defined descriptio
When the current translation field is edited in the company attribute translation window for an account, the account description cannot be changed from the accounts window. This behavior can be observed in other windows too: tax codes window, customer invoice types, supplier invoice types.Is it possible somehow to change such descripotions in desired languages? There is a workaround. But it is not effective too in certain instances.Workaround is: If the account description needs to be edited, use the company attribute translation window and change the relevant row with the language code.If more languages are used as the login language, then, add them to the ‘Company attribute translations’ window and edit the current translations of those as well. Issue with the suggested workaroundIf the user login from a language which is not defined in the company attribute translation window, then the old account number is shown. (If it’s a system defined account, then the system defined descripti
After our recent cloning from a Single Instance (PDB) to a RAC, we found almost 75 SYS DB objects being invalidated, which resulted in more invalid objects in the IFSAPP schema (175 in total).Recompiling the invalids won’t work as well, and it will still remain invalidated after force validations too. The RAC cluster is installed within Oracle Linux 8.5 which is Oracle verified, and the Oracle version of the DB is 19c E.A. Release 19.0.0.0.0 - Production [Version 19.14.0.0.0]Has this situation been seen by anyone, and which solutions \ suggestions do you have for us to solve it immediately? Thank you in advance.
When the RMB “Validate Tax ID number” on Supplier>Address>Document Tax Information intermittently hits the below error.Tax ID Number ******** cannot be validated due to network problem.Further investigations:The error mostly occurs when the action performed perpetually The validation actually executes via the client (tbwSuppDocumentTaxInfo.cs) Looks like a client limitation (threshold for MS_MAX_CONCURRENT_REQ)Has this every happened to you?Any clue will be highly appreciated.Thank you.
I’ve already found few KBAs which discuss similar topics but none of them were answered with the exact scenario with migrating personal profiles from one environment to another in bulk, hence this community post.We need to find an alternative way to migrate personal profiles instead of manually exporting and importing one at a time which consumes a lot of time and of course not feasible for our IT department. It’s not practical enough to hand the responsibility over to end-users with the necessary grants, which isn’t again a good solution in many aspects.Do you have any bright ideas where we can migrate personal profiles in bulk across environments?Thank you in advance./Manulak
When creating a .NET interface (C#) using the standard OData connected service library, the standard way to set the data time is to use the very own type DateTimeOffset. DateTimeOffset now_ = DateTimeOffset.Now;hu.Loaded = now_;But, this ends the request up with ODP_DESERIALIZATION_ERROR. The connector we use: OData Connected Service - Visual Studio Marketplace If that’s not supported by IFS, what is IFS’s standard and supported OData connecter for .NET applications?If that’s supported, is there a bug fix from IFS to overcome this issue?Thank you Sample code:
The corresponding application message of the queue NOTIFICATION errors out with the following error when the recepient email address contains control characters (Ex : webmaster@minimax.de) or umlauts (Ex: webmaster@kältetechnik.de). Error while sending data… Caused by : javax.mail.internet.AddressException: Domain contains control or whitespacesHowever, lot of our customers have umlauts in their email addresses, and it’s not clear which javax package IFS users within the framework for email sending, and supports which RFC versions.(Ex: is it javax.mail:mail or com.sun.mail:javax.mail , etc)Do we have a pre-defined set of characters which should be escaped (marked as invalid for use within IFS emails) or if there’s knows control character limitation (or double-byte character limitation)?
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
