on
RE:
How much longer until this is implemented...Something that is pretty simple to do in Excel should be elementary in PBI.
RE:
It makes no sense that this would not be on the roadmap. It essentially renders the employees area useless in countries other than where it has been properly localised.
RE:
This feature has to be prioritised and implemented asap.
RE:
We need this functionality soon.
RE:
I second that. How can we be notified of new Power BI gateway releases?
RE:
Need this functionality soon.
RE:
These two should be separate Legends of Line chart. Legend 1: color-byLegend 2: shape-byWe already have legend for Colorby but would need legend for Shapeby (aka Dashby).
RE:
Yes this would be helpful, I voted with my personal account but would use it in my work account.
RE:
Having Report Selections for as many reports as possible is always a great idea. This gives BC a lot of flexibility!
RE:
Enabling batch processing for fixed asset journal processing is an important issue which needs attention. The feature 'Automatic split of large financial journals'' feature is now enabled by default meaning you cannot post fixed asset depreciation journals over 1000 lines without using the GL > Journal Entries > Post journals function. This function is prone to user error as users must use the "Select" query instead of 'ticking' to select the lines that you wish to post as the 'look and feel' of the form implies.Additionally, using this function seems to assume users have permissions to post all types of financial journal. In an environment where there is segregation of duties, via security permissions, giving this form to a user who is permitted to post fixed asset transactions but not other types of financial journal is not an acceptable workaround. Finally, enabling batch processing for fixed asset journals would provide a more consistent user experience across each of the finance modules.