on
RE:
It would be great if we could have dynamic support for multilingual lookups in marketing forms. Allowing the "PrimaryNameAttribute" to change based on the selected language would eliminate the need for multiple forms and streamline multilingual form management, providing a better user experience.
RE:
I'm interested to hearing from my colleagues who are using Power BI and dealing with this issue. How are you able to overcome this? I worry about providing reports to clients, who are going to see out of date slicers and filters. Imagine if you opened booking.com and they defaulted to a date in 1999 for example. I think that's a good example of where Power BI is today.
RE:
This feature would significantly simplify multilingual form management and increase flexibility for global use cases. I believe it would add great value for businesses with international operations.
RE:
Brilliant!It will surely give us an affordable option to better assist our clients
RE:
It´s essential and wil open many ports we don't have today.
RE:
I totally support this proposal as it helps the business in aligning the business processes. System users do not have to maintain the same information in 2 areas and also unified pricing offers much more flexibility in defining the sales promotion programs.
RE:
I agree. Please MS, add this to Real-time.
RE:
An idea like this sitting for 5 years is exactly why I no longer put anything in Experiences. Not having kilometres as a display choice leads to users thinking they have to convert their kilometres to miles. Sure I can make a view and publish it out to everyone, but I can't do that on the mobile app and even workspace re-imagined has forms with no views can be published.
RE:
Agreed, this is absolutely required! This allows for a great deal of manual error, not to mention is not a nice feel for the users when sifting through hundreds of numbered warehouses.
RE:
Agreed, should entail all modules. It is very limiting to have to select the fixed option for all main account activity.