Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
We have a customer where a lookup on the Account is related to Payment terms(entity). On the Payment terms, we have the fields: name, language and ERP and code. So for each new language, there has been added new names of the payment terms for e.g 30 days net (eng), german tage netto. So right now there is 700 payment terms record, most of them the same but different languages.
To my point, Is this really a smooth way of doing this? How would you approach this? Could an option-set be a thing? Payment terms have an integration with the ERP.
Thank you for your time!
Option set could work, because they allow for translations for the text values. The language shown depends on the interface language selected by the user. But this might not be desirable if users want to see the user interface face in English regardless of the language for Payment.
I think the answer depends on who needs to see the text in the relevant language.
Also on your Payment entity, you say you have four fields. Of course with the option set, you'll only have one value - so you'll perhaps need to bring the other three fields onto the account entity.
Business Applications communities