RE:
Not sure changing Location to Warehouse is a good idea. Firstly this will cause a lot of confusion for existing users and secondly a Location In BC could be an In-Transit Location, Van Stock, a sub-division of a physical warehouse, Free on Board stock, etc, so in a lot of cases a location would not actually be a physical warehouse.
RE:
We need to be able to decide the corrective action to take on problematic reports over-consuming CUs. There is a total usage report but is ambiguous as the report only calculates based on the capacity ID (instead of the total usage of the system). Basically requiring the user to run the report for all the capacity ID's they own and manually add the data together.A better option will be to have the report look at the entire tenant, and group by Capacity, Workspace and then report.
RE:
wondering if there was any update on this - we do a number of annual contracts with monthly payments required and this would save us creating 12 invoices or one invoice that looks overdue
RE:
I do not think that this a good idea, because a location could be the car of a service employee, an oil tank buried outside in the ground, the service bag, a workplace, or any other place you can/may define. So it should not be defined and understand as a warehouse.
RE:
Definitely it's a great addition to have Git integration for dataflow. Data flow is going to be a greate ETL tool in Fabric and needs to manage the versions of the changes.
RE:
This is the document: https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-admin-center-environments#linked-power-platform-environment
RE:
The more I use Power BI the bigger this issue becomes. A chart should either start by default on the right with the most recent data or this should be provided as an option. It seems like a simple one to fix, please Microsoft !
RE:
Supporting regular expressions in M code, would make cleaning data so much more efficient and flexible. M code has some good inbuilt functionality to clean and trim code, but native Regular expressions would allow things to be done succinctly in one step instead of many. Plus, regular expressions are already well known to us who have used other languages such as SQL, Perl, JavaScript, Python, R etc.This is my biggest bugbear with M code.
RE:
This shall be a great addition to ADP Connector and People Analytics Offerings.
RE:
I am shocked to discover that they seem to "used" to have one but removed it for some reason?? https://community.fabric.microsoft.com/t5/Desktop/Microsoft-Histogram-Chart/td-p/2971391I second that this is a very very basic visualization that I expected to be a part of the product.