on
RE:
+1
RE:
I agree. It is very powerful option, that definitely should be added!
RE:
I understand you both, but also think that the word 'Location' is too general. It does not refer to the fact that it is something to store stuff?! And I prefer to explain that a service engineers van can also be a 'Moving' Warehouse. Any change in these naming will definitely create some confusion I also agree with.In Dutch the naming might even be worse then in English BTW.
RE:
Would it be possible to add a status to the workflow condition so you can exclude this record restriction applied after the BACS import from the workflow conditions. - Therefore it would bypass the workflow.As per the comments prior to mine - There's no benefit to the operation as it stands and it's causing an additional unnecessary step to this process of posting a payment journal.
RE:
Exchange rates should be stored in GL Entries. Such exch rates should also be presented in GL Detail Transaction Reports.
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.