Hi Team,
I have a requirement to translate the language for specific fields form Arabic language to English in the staging table. Middleware team doesn’t have the capability to do the translation.Can anyone help to handle through X++ .
Please tell us more about your requirements. Do you mean that you want to automatically translate data (with something like Google Translate) when exporting them through a data entity?
Do you mean that
Hi Martin,
Requirement is to export the invoice details to the external system.In D365 we have multiple legal entities.In D365 tables all the data stored in the local language they want to do the conversion in the staging table before sharing to the middle ware. No entity/Api involved here.
You’ll need to think about what it means “to do the conversion”. It’s even vaguer than before.
Also, F&O uses data entities to export data. Why do you reject using an entity and how else do you imaging doing the export?
Hi,
It’s not only sharing the invoice,I need to export the party and bank addresses.Need to add the type differentiator whether it’s vendor ,bank or customer address., Instead of using entity I felt comfortable in inserting the records into staging table from dirpartypostaladdress view. In D365 party address field I should convert to english format when it get inserted into the staging table.
You again said almost nothing about the topic of this thread (Translate the language from Arabic to english). You can’t start designing a solution before you have a better understand of the business requirements than that you want to somehow convert something.
But the idea of translating the address is suspicious. Will the result be good enough for legal purpose (you’re talking about invoices), to get mail delivered and so on?
By the way, the usual way to populate a staging table before exporting to a file is… using a data entity. It’s the way how data management in F&O works.
Hi,
Screening the address is the business expectation . Third party system can only screen english format.