Comments
We've tried to work around this by creating separate views, after creating columns for specific languages, and putting the different language in the view, and then qualifying the view by a specific security role, which is also assigned to a user. However, since the "Name" column is the lookup value, there needs to be a default view for lookup. The security role setup did not impact the view used as the default so even though the security role didn't grant access to the view, somehow we still had access to the view. There is no fallback view in the configuration like with forms that have security roles assigned. Even with java script to switch the view, the "Name" is still the display name. The solution needs to translate the data on the fly based on the user's language and not display the base language.
Hi, does anyone know what the current status of the issue is? The GitHub link is no longer valid, but we assume it remains unsolved, as we keep experiencing the same issue in the Czech localization. We opened a ticket with Microsoft Support, and they simply admitted there are some fields that are not being translated from the default language because they don't reference the table with translations, and that was it.
This is crucial functionality and bottleneck in RTM for Event management. Without the access to Lead & Contact audience we are missing opportunity to capture important attributes for Lead management purposes, as well as lacking insights. That will result in huge amount of manual work for event owners to get proper data for Sales teams.
Business Impact: Bio-Rad has a global queue for all regions; therefore, alerts of one team/region will be sent to all the supervisors (all regions) working at that same time; which will cause major confusion and dis-satisfaction.Therefore, it's required to allow flexibility in our deployment and many other case scenarios that can arise from this.