This post is going to cover how to create products and services in FieldOne Sky for Microsoft Dynamics CRM 2016.
After installing FieldOne Sky additional fields are added to the product entity to support FieldOne’s extended functionality. The fields that are used will differ depending on the product being an inventory item, non-inventory or service.
First of all, it is important to understand that each product or service has a status. When initially created that status is draft. Whilst in draft status the product will not be available to work orders. Only once the product has been published does it become available.
Once published you can continue to edit the product details but there may be an occasion when you want to temporarily stop the use of the product whilst it is updated. In this situation you use the “revise” option, which gives the product a status of “Under revision”. And therefore makes it not available to work orders.
When a product or service reaches end of life it should not be deleted, the status is changed “Retired”.
Now let’s look at a Service, as that has less fields. Below you can see
|ID||This is a field that identifies the product or service , and is mandatory.|
|Product name||A short descriptive name for the product or service.|
|Subject||Optionally you can relate products to you subject tree|
|Quantity on hand||You can enter the qty on hand in this field but this is not the inventory qty used by FieldOne Sky. FieldOne Sky inventory has a concept of warehouses and we can then see the qty on hand in each warehouse. Inventory management within FieldOne Sky will be covered in a separate blog post.|
|Unit Group||This is the unit group of the product; unit groups are used if you need to stock and sell products in specific quantities. (Such as dozens, pairs etc.)|
|Default Unit||The default unit is the default or primary unit from the selected unit group.
If you stock and sell product in “ones”, then keeping the unit group and default unit as the system default values shown will work.
|Product type||This is the standard CRM product type. Values include “Sales Inventory”, “Miscellaneous Charges”, “Services”, “Flat Fees”.
This field can be used to help categorize types of product but it has no functional purpose from a FieldOne Sky point of view.
|Default Price List||This is a system recommended field but from a FieldOne Sky point of view I have found no functional implication of setting this field. Prices are driven from the price list selected on the work order. And if the product isn’t in the selected work order price list the “list price” is used.|
|List Price||As mentioned above this is the price that will be charged for this product if no price list item price exists.|
|Currency||The currency used for the list price and cost values for this product or service.|
|Decimals supported||How many decimals are required in monetary values for this product or service.|
|Standard cost||Typically the average cost over a given period of time.|
|Current cost||The current cost.
Both standard and current cost fields can be used to drive prices in the price lists using a percentage margin or mark-up.
|FieldOne Product Type||This can be “Service”, “Inventory” or “Non Inventory”.
When set to Service then many of the fields such as “default vendor” are not required and become locked. As shown on the example above.
|Printable||Can be yes or no. This field is used to show if a product or service can be included in a FieldOne work order or not. Meaning, all of your products that relate to work orders will need to be “printable”.|
|Taxable||Is this product liable for sales tax?|
|Account reference and GL accounts||Optional references that could be used to relate this product suitable codes in your account systems.|
Below is an example of an inventory product for FieldOne Sky. Inventory and non-inventory products have additional values available that help support purchasing. Including holding details of the vendor who supplies the product, the name and part number used when purchasing and the products manufacturer.
For inventory and non-inventory products you can also store a model number and UPC Code (barcode) for the product.
And if the product should convert into a customer asset. I will cover this concept in more detail in a future post. FieldOne Sky contains a concept of customer equipment (assets). You may want to0 use this to record what equipment a customer has on-site. For example: If you installed an air conditioning unit for a customer you many want to record its details against the customer, as that could be useful for future service requests etc.