Comments
Other scenario to consider, an engineer will have a specific type of vehicle (with dimensions) to reach a service location.For example: a service van with a specific width, height, and weight.RSO should be able to consider these "vehicle" dimensions (constraints) in combination with actual map data to facilitate the optimal route and usage of the organization resources. Besides width, height, and weight, you could also consider "emission" legislations. Certain cities won't even accept certain vehicles to enter if they don't comply with emission norms.Some EU examples:Low emission Zone - Berlin.deLow emission zone for diesel vehicles only - City of AmsterdamLow Emission Zone | City of Brussels
This feature is definitely needed. Many companies have multiple warehouses where Purchase and Sales pricing is different depending on the freight input. In an ideal Distribution environment you would not price the same for a customer delivery in California as you would for a delivery in New York with product being purchased from Maryland. Freight costs and addition SG&A costs would be different based on the regions.The fact that this feature is missing is our biggest criteria when evaluating whether we choose Business Central or Acumatica which does include this feature.