Martin Fux Coordinator Global Sales

Martin Fux

Joined: 12/20/2023

  • Business Unit Entity Available as Hierarchical Entity in Forecast

    Mon, 21 Dec 2020 08:10:40 GMT – Dynamics 365 Sales – Completed 

    The Business Unit entity is not defined as hierarchical entity and it cannot be changed to a hierarchical entity. Hence it cannot be used as hierarchical entity in Forecasting. This would be useful to be able to break down the forecast into organizational units.

  • Create Lead or Contact by Scanning Business Card QR Code

    Thu, 16 Dec 2021 14:03:48 GMT – Dynamics 365 Sales – New 

    We have implemented the business card scan functionality that comes out of the box with Dynamics for Sales. Our users approach us more and more frequently with the request to be able to create the Lead by scanning the QR code printed on more and more business cards they receive from customers. The advantages are quite obvious: no more typos or information in the wrong field A Bing search yields many sources with additional information on this topic.

  • Allow User to Choose Unit when Adding a Product

    Mon, 23 Jan 2023 17:01:39 GMT – Dynamics 365 Sales – New 

    Hi,


    it would be great if users could select one of the units of a unit group when adding a product.


    Today the unit of an Opportunity Line / Quote Line is determined by the unit of the respective Price List Item. Since Unit Groups can hold calculations between units of the same type (i.e. length) it would be fairly simple to allow the user to select the unit of a Product suitable for the customer and have D365 do the calculation in the background.


    Example:

    Product Cable is entered in the price list item of Price List A in meters and price 10 USD / meter

    In a Quote with Price List A selected a user in Asia selects 2 meters of the Cable, hence the price shall be 20 USD

    In a Quote with Price List A selected a user in US selects 2 yards of the same cable, hence the price shall be 18.28 USD


    In the current setup there are multiple complexities to achieve this:

    1. One Price List is required for each currency that we would like to quote in and for each measurement system (metric, imperial), doubling the amount of Price Lists
    2. if the master application for products (typically an ERP) holds the prices in metric units a calculation needs to be implemented to correctly set unit and price per unit for price lists with imperial units

    Martin

  • Opportunity to Work Order Process

    Tue, 09 Jan 2024 12:35:30 GMT – Dynamics 365 Field Service – New 

    Currently a Work Order needs to fulfill multiple conditions with regards to currency to be created without errors:


    • Transactioncurrency must be the currency of the Billing Account (note that by default behavior the Billing Account field is filled with the Service Account by OOB functionality if left blank by the user)
    • Price List must be in the currency of the set as transactioncurrency of the Work Order
    • Price List in Work Order Type must be in the currency of the transactioncurrency of the Work Order, if the Price List is empty on Work Order Type OOB functionality tries to set NULL as Price List in Work Order


    All these automations cause issues when you have customers that regularly pay in different currencies. The decision of our customer is based on


    • from which of our subsidiaries they purchase
    • if there is a frame agreement in place for the products / services they purchase; the frame agreement fixes prices in a specified currency
    • financial considerations of our customer (i.e. better x-rate or cash availability in one currency than another)


    The problems that arise are as follows:

    • When user changes Work Order Type and the Price List is empty in Work Order type or not in the same currency as in the Work Order error message pops up; means either we need one Work Order Type per currency (approx. 100), making it 900 Work Order Types instead of 100 or we need to prevent user from changing Work Order Type


    Suggestion: if the Price List field on Work Order Type is NULL, just ignore it, don't try to overwrite what is in Work Order already.


    When creating a Work Order from Opportunity the following happens due to the setup described above

    • Customer in Opportunity is in base currency
    • Opportunity is NOT in base currency, but in currency A
    • Opportunity Price List is in currency A

    Suggestion: when creating Work Order from Opportunity with the OOB functionality there is an error message warning me about the currency inconsistency


    Suggestion: the currency of the Account in Opportunity (which becomes the Service Account and the Billing Account) should not be used to check for inconsistencies. Or there should be a setting in which the administrator can allow the inconsistency


    This is also a topic for the announced Quote to Work Order functionality.


    Remark: when creating a Quote and then a Sales Order from an Opportunity the only check with regards to currency is that the Price List currency is the same as the currency of the Opportunity, Quote, Sales Order respectively. This behavior would also be good for Work Order.

  • Provide a Switch to Disable Warehouse Functionality

    Thu, 08 Feb 2024 16:41:19 GMT – Dynamics 365 Field Service – New 

    The Warehouse and purchasing processes are covered by our ERP, so the Warehouse functionality is redundant and causing issues in D365 Field Service.


    Would it be possible to make the Warehouse functionality configurable, at least on/off?


    The issues we face are as follows:

    • Warehouse becomes mandatory field on Work Order Product when Line Status is set to "Used", but since we are not using the Warehouse functionality this is additional input for the users
    • When users select the default Warehouse a warning pops up informing about negative stock for the Product
    • Product inventory records are created, but in our case they are not used, just consuming storage